Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fdc45e7ebc06f7dd56423912227a6465ecee55a4d64ea4fcc4e7e152e2c0789

Tx prefix hash: 0d147b1c80d68d8f0de8af108d0136626b9270f2cc6365294098a8d83d9ac38b
Tx public key: 94e87db81b861f6552e77eb8da6d0a4e14b75b8b863e73606ebbac29f87fc189
Timestamp: 1756180327 Timestamp [UCT]: 2025-08-26 03:52:07 Age [y:d:h:m:s]: 00:132:05:41:11
Block: 1354586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94508 RingCT/type: yes/0
Extra: 0194e87db81b861f6552e77eb8da6d0a4e14b75b8b863e73606ebbac29f87fc1890211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a22dad5ef6ea3d057e9cae4e7908c1acd1727a52780faa97dde1062d27a44c7 0.600000000000 1842575 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": 1354596, "vin": [ { "gen": { "height": 1354586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a22dad5ef6ea3d057e9cae4e7908c1acd1727a52780faa97dde1062d27a44c7" } } ], "extra": [ 1, 148, 232, 125, 184, 27, 134, 31, 101, 82, 231, 126, 184, 218, 109, 10, 78, 20, 183, 91, 139, 134, 62, 115, 96, 110, 187, 172, 41, 248, 127, 193, 137, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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