Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10d36afcaa359da90469f05448fc3e109a3419fed75c79c3caa90a548376674b

Tx prefix hash: 51b6cf4a0e8ce06d2b50694f6b48066ed565897d860a3ba42230661d0563751c
Tx public key: 8dc4bec6acd116d1f5124689141b40f9385b70d2f3fcc408ab4d875b5f1b9eef
Timestamp: 1760930526 Timestamp [UCT]: 2025-10-20 03:22:06 Age [y:d:h:m:s]: 00:075:09:29:20
Block: 1393791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53967 RingCT/type: yes/0
Extra: 018dc4bec6acd116d1f5124689141b40f9385b70d2f3fcc408ab4d875b5f1b9eef02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c70c7402ffcc58f2d021299d6cecb0a602088317b7a649b4378a186ea036e78 0.600000000000 1882058 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": 1393801, "vin": [ { "gen": { "height": 1393791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c70c7402ffcc58f2d021299d6cecb0a602088317b7a649b4378a186ea036e78" } } ], "extra": [ 1, 141, 196, 190, 198, 172, 209, 22, 209, 245, 18, 70, 137, 20, 27, 64, 249, 56, 91, 112, 210, 243, 252, 196, 8, 171, 77, 135, 91, 95, 27, 158, 239, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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