Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3895e0846416915b403b588afca7570ae641e4714e87d9df6b948752fae737a8

Tx prefix hash: bd80ab1a535d4761672e3fdf200378536a92df73d331028ebd7abd8e25ad9fff
Tx public key: 092391c308aafc518b8d7c1e01341d974269c9d157e4b54fd7822cf505526e8d
Timestamp: 1763930980 Timestamp [UCT]: 2025-11-23 20:49:40 Age [y:d:h:m:s]: 00:004:12:44:57
Block: 1418643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3241 RingCT/type: yes/0
Extra: 01092391c308aafc518b8d7c1e01341d974269c9d157e4b54fd7822cf505526e8d021100000008d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e5b72469672b63c13e27061aaf769e632f9735a925ea6d9ea18d7399d6354ba 0.600000000000 1907176 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": 1418653, "vin": [ { "gen": { "height": 1418643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e5b72469672b63c13e27061aaf769e632f9735a925ea6d9ea18d7399d6354ba" } } ], "extra": [ 1, 9, 35, 145, 195, 8, 170, 252, 81, 139, 141, 124, 30, 1, 52, 29, 151, 66, 105, 201, 209, 87, 228, 181, 79, 215, 130, 44, 245, 5, 82, 110, 141, 2, 17, 0, 0, 0, 8, 214, 225, 157, 124, 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