Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0d466f7b4501701073c218279870a0839c5f25722dfddda86f1c4ad4192c2518

Tx prefix hash: e407700bbc87961583e09bf6fa705c29e81856f29354f815c00ac5f3bd62ac92
Tx public key: ab8f7257fca2c98647c6d3449d3e82b30a3743e6d1a69b8666bc3052a72e8c86
Timestamp: 1685970508 Timestamp [UCT]: 2023-06-05 13:08:28 Age [y:d:h:m:s]: 02:156:07:47:31
Block: 775679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 631507 RingCT/type: yes/0
Extra: 01ab8f7257fca2c98647c6d3449d3e82b30a3743e6d1a69b8666bc3052a72e8c8602110000000133af99f4000000000000000000

1 output(s) for total of 1.651405166000 dcy

stealth address amount amount idx
00: 63fc9bb140911a1a08f56e8a6db22ccfe613523581ccf29e34a1ecbcb150771d 1.651405166000 1225200 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 775689, "vin": [ { "gen": { "height": 775679 } } ], "vout": [ { "amount": 1651405166, "target": { "key": "63fc9bb140911a1a08f56e8a6db22ccfe613523581ccf29e34a1ecbcb150771d" } } ], "extra": [ 1, 171, 143, 114, 87, 252, 162, 201, 134, 71, 198, 211, 68, 157, 62, 130, 179, 10, 55, 67, 230, 209, 166, 155, 134, 102, 188, 48, 82, 167, 46, 140, 134, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8