Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ba80a7b5def59af297a8737ba28d7b5c3d83733ad3c8c86e4e4b0352a98bf9c

Tx prefix hash: 73752633c7a1299b30afb6817ebdd730fd92ffd2eb13953a31f3b280fe8d3b2d
Tx public key: ad473e503d3557a97c4a788ba8b33603efaf214dd962d7a074e88a4c0bf6ed2a
Timestamp: 1755060956 Timestamp [UCT]: 2025-08-13 04:55:56 Age [y:d:h:m:s]: 00:105:09:01:12
Block: 1345842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74734 RingCT/type: yes/0
Extra: 01ad473e503d3557a97c4a788ba8b33603efaf214dd962d7a074e88a4c0bf6ed2a021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1374c26c5961826c6a04f38e4d88ae748fdb441c59fc6effe0a0ecfc853b0dc5 0.600000000000 1833737 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": 1345852, "vin": [ { "gen": { "height": 1345842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1374c26c5961826c6a04f38e4d88ae748fdb441c59fc6effe0a0ecfc853b0dc5" } } ], "extra": [ 1, 173, 71, 62, 80, 61, 53, 87, 169, 124, 74, 120, 139, 168, 179, 54, 3, 239, 175, 33, 77, 217, 98, 215, 160, 116, 232, 138, 76, 11, 246, 237, 42, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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