Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d12d91a2362f211e9db5f52665db968646f0532558225fc3df24fb31bf517a2

Tx prefix hash: d5af22d413aa5e42a5aa5b3afa85863d72b25cd7c30f6ad9628d194212375db3
Tx public key: 73f8c9cf9fc2c47423d48e989f4d95d05a3dcd5803077de68102253b5893ee7b
Timestamp: 1745363645 Timestamp [UCT]: 2025-04-22 23:14:05 Age [y:d:h:m:s]: 00:206:21:34:43
Block: 1267313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145594 RingCT/type: yes/0
Extra: 0173f8c9cf9fc2c47423d48e989f4d95d05a3dcd5803077de68102253b5893ee7b02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f33516b4dcebccd0d716efb24bbee02d0c34d76d0dbaf816ad1a03e1c235c3a 0.600000000000 1754542 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": 1267323, "vin": [ { "gen": { "height": 1267313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f33516b4dcebccd0d716efb24bbee02d0c34d76d0dbaf816ad1a03e1c235c3a" } } ], "extra": [ 1, 115, 248, 201, 207, 159, 194, 196, 116, 35, 212, 142, 152, 159, 77, 149, 208, 90, 61, 205, 88, 3, 7, 125, 230, 129, 2, 37, 59, 88, 147, 238, 123, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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