Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f72a3d74aed3a670328791ca8560ccfd042de711dc04285645a5de0dc8ecb736

Tx prefix hash: 814154d564167ee948133528e354514bfc2c0fdd36332ab8fa94bd7497e39e61
Tx public key: 15ac039920e4c98a8c603dbc326d1afb49cbec5f4bb00d4b4494b0f80700952f
Timestamp: 1751648352 Timestamp [UCT]: 2025-07-04 16:59:12 Age [y:d:h:m:s]: 00:137:21:09:21
Block: 1318728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96843 RingCT/type: yes/0
Extra: 0115ac039920e4c98a8c603dbc326d1afb49cbec5f4bb00d4b4494b0f80700952f021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17bf6e4f2b6d1d4dbc2b1ca7108825d13746550a38dccce997699b0ccea73f65 0.600000000000 1806413 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": 1318738, "vin": [ { "gen": { "height": 1318728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17bf6e4f2b6d1d4dbc2b1ca7108825d13746550a38dccce997699b0ccea73f65" } } ], "extra": [ 1, 21, 172, 3, 153, 32, 228, 201, 138, 140, 96, 61, 188, 50, 109, 26, 251, 73, 203, 236, 95, 75, 176, 13, 75, 68, 148, 176, 248, 7, 0, 149, 47, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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