Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bdad716de434f69c3f7d344c4e96db4e13ac773a7646f6aa9c4ac0f34dba41b

Tx prefix hash: 51df09f21f4e4c549d5355fc9e8ee27160d36f7da56af67885e3bacb4ae55c14
Tx public key: 0bcd159a7978a7c3fc6350f9fd3f3442cf7786c1ddac4d6887eb0ff5de2af077
Timestamp: 1748945518 Timestamp [UCT]: 2025-06-03 10:11:58 Age [y:d:h:m:s]: 00:219:23:21:08
Block: 1296989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154966 RingCT/type: yes/0
Extra: 010bcd159a7978a7c3fc6350f9fd3f3442cf7786c1ddac4d6887eb0ff5de2af07702110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1764d028051c10ef938120dd7a4b491bb51cc6a6a6cd30b7acbc99672897bbab 0.600000000000 1784506 of 15

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": 1296999, "vin": [ { "gen": { "height": 1296989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1764d028051c10ef938120dd7a4b491bb51cc6a6a6cd30b7acbc99672897bbab" } } ], "extra": [ 1, 11, 205, 21, 154, 121, 120, 167, 195, 252, 99, 80, 249, 253, 63, 52, 66, 207, 119, 134, 193, 221, 172, 77, 104, 135, 235, 15, 245, 222, 42, 240, 119, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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