Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5b9cc012688d263d89b7c7ff61feaa999fee4cc8f405990033d2069d1818ec0

Tx prefix hash: 1c945ea1f4d644de0ed4e46330b3e0a64c7f1e0243c7b3e6c1e1e94c9964175d
Tx public key: 2bce478811f5ea528d1f122cc9f2d9f2adebbd4df2b881d244616d9196eb2fd2
Timestamp: 1761850972 Timestamp [UCT]: 2025-10-30 19:02:52 Age [y:d:h:m:s]: 00:013:17:19:02
Block: 1401413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9813 RingCT/type: yes/0
Extra: 012bce478811f5ea528d1f122cc9f2d9f2adebbd4df2b881d244616d9196eb2fd202110000001125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eec635d359c12985a3d1ddf795b844f2b4ebb350f76e038474f1c7801b3434dc 0.600000000000 1889732 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": 1401423, "vin": [ { "gen": { "height": 1401413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eec635d359c12985a3d1ddf795b844f2b4ebb350f76e038474f1c7801b3434dc" } } ], "extra": [ 1, 43, 206, 71, 136, 17, 245, 234, 82, 141, 31, 18, 44, 201, 242, 217, 242, 173, 235, 189, 77, 242, 184, 129, 210, 68, 97, 109, 145, 150, 235, 47, 210, 2, 17, 0, 0, 0, 17, 37, 163, 90, 15, 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