Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5cf367a8743f552f134dd6ab2d19fdf912ea61fc73b7069aa677257ecf7056e

Tx prefix hash: 28153d3a4216ba67888db57580c9aaa09ec5bd323caec832cb84c643a75ff08e
Tx public key: d4f6c9d24609a76cd1b895fc1cbb7acca052a61c777793c3cd8fe66ccb304984
Timestamp: 1737276765 Timestamp [UCT]: 2025-01-19 08:52:45 Age [y:d:h:m:s]: 00:150:17:22:47
Block: 1200601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107445 RingCT/type: yes/0
Extra: 01d4f6c9d24609a76cd1b895fc1cbb7acca052a61c777793c3cd8fe66ccb304984021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbfca968a6fc76c513b1ea00d783b365ccb0527458e5ea32d503b43c5c8725a2 0.600000000000 1687246 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": 1200611, "vin": [ { "gen": { "height": 1200601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbfca968a6fc76c513b1ea00d783b365ccb0527458e5ea32d503b43c5c8725a2" } } ], "extra": [ 1, 212, 246, 201, 210, 70, 9, 167, 108, 209, 184, 149, 252, 28, 187, 122, 204, 160, 82, 166, 28, 119, 119, 147, 195, 205, 143, 230, 108, 203, 48, 73, 132, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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