Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef81d5dd09e897c945ba7c4a904149ecb7b9280efa3c1e8927d0a4bffb09c3cd

Tx prefix hash: a45b043e373a9c5df7d3b751c533f83d5affa36f1a4f555783cc7e2a12b80d34
Tx public key: 3e29d140ce922f5357e92e9d6115a54a615620d3fc73dfbd634b1d18d61ae89e
Timestamp: 1765550066 Timestamp [UCT]: 2025-12-12 14:34:26 Age [y:d:h:m:s]: 00:011:11:48:32
Block: 1432055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8213 RingCT/type: yes/0
Extra: 013e29d140ce922f5357e92e9d6115a54a615620d3fc73dfbd634b1d18d61ae89e021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 651f161301d4db4c17b8a9458218b7755a0f2e03f0aace36ee7720fec251d451 0.600000000000 1920834 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": 1432065, "vin": [ { "gen": { "height": 1432055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "651f161301d4db4c17b8a9458218b7755a0f2e03f0aace36ee7720fec251d451" } } ], "extra": [ 1, 62, 41, 209, 64, 206, 146, 47, 83, 87, 233, 46, 157, 97, 21, 165, 74, 97, 86, 32, 211, 252, 115, 223, 189, 99, 75, 29, 24, 214, 26, 232, 158, 2, 17, 0, 0, 0, 4, 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