Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd9ac835ccdb078c18d68bac5db71e30ffaceca215176a0a500f69e60bd54edc

Tx prefix hash: b5174dc5f1bd04cc7694589e122dde6b43a9ff9160f9cb6eb9f5897ed80a03eb
Tx public key: 461dd92405c0ba4d1b0b7a611f3b5206b72f3208ebde14b4f7031cf0473c22fa
Timestamp: 1761978446 Timestamp [UCT]: 2025-11-01 06:27:26 Age [y:d:h:m:s]: 00:069:02:00:06
Block: 1402482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49446 RingCT/type: yes/0
Extra: 01461dd92405c0ba4d1b0b7a611f3b5206b72f3208ebde14b4f7031cf0473c22fa021100000006df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ee746f3c4a1f338fe8bc8a29d5869a0d0ba9931ed204e0d3449c5bbb2930a28 0.600000000000 1890801 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": 1402492, "vin": [ { "gen": { "height": 1402482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ee746f3c4a1f338fe8bc8a29d5869a0d0ba9931ed204e0d3449c5bbb2930a28" } } ], "extra": [ 1, 70, 29, 217, 36, 5, 192, 186, 77, 27, 11, 122, 97, 31, 59, 82, 6, 183, 47, 50, 8, 235, 222, 20, 180, 247, 3, 28, 240, 71, 60, 34, 250, 2, 17, 0, 0, 0, 6, 223, 90, 36, 122, 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