Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 276c69cc61cc1bf74d6082f44e170b195d7b5f8e8e5fc145cdda3d43cd84876b

Tx prefix hash: bc8c10f58db56649bc62d50ca989661f5bd39294ddc1cf7ac6ad8ad4088b452a
Tx public key: 00dea5bf4d416b3af5b0e7b663501f1baa93f7e25ada86fc3bbab4f5b357932f
Timestamp: 1749159923 Timestamp [UCT]: 2025-06-05 21:45:23 Age [y:d:h:m:s]: 00:159:12:09:08
Block: 1298755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111678 RingCT/type: yes/0
Extra: 0100dea5bf4d416b3af5b0e7b663501f1baa93f7e25ada86fc3bbab4f5b357932f02110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1e34ba4c27401c2442a20163a8faa129062495b61714a2aee21ce01e135d8d3 0.600000000000 1786286 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": 1298765, "vin": [ { "gen": { "height": 1298755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1e34ba4c27401c2442a20163a8faa129062495b61714a2aee21ce01e135d8d3" } } ], "extra": [ 1, 0, 222, 165, 191, 77, 65, 107, 58, 245, 176, 231, 182, 99, 80, 31, 27, 170, 147, 247, 226, 90, 218, 134, 252, 59, 186, 180, 245, 179, 87, 147, 47, 2, 17, 0, 0, 0, 1, 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