Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60a5024a9212358b10ea9af1013ffda2403b38d3c4fa61bcf65aaa5ec54fa99b

Tx prefix hash: 21ed8ca5477ab463c5a2b518945d310b3804dc02cf5fdef8a56f9c626445cb8c
Tx public key: a38b008ed353b2cbf8223c13ccd5c28cddd5d4e60a3c56e2c8f996473b92b73b
Timestamp: 1669157839 Timestamp [UCT]: 2022-11-22 22:57:19 Age [y:d:h:m:s]: 02:061:16:56:26
Block: 636949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 565999 RingCT/type: yes/0
Extra: 01a38b008ed353b2cbf8223c13ccd5c28cddd5d4e60a3c56e2c8f996473b92b73b02110000000275e3f0e9000000000000000000

1 output(s) for total of 4.759086062000 dcy

stealth address amount amount idx
00: 3bfa116dc8624a7b44bc4b3cd6b01f91aa9d0df525ea164f9f744a18a36b74fa 4.759086062000 1076437 of 0

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": 636959, "vin": [ { "gen": { "height": 636949 } } ], "vout": [ { "amount": 4759086062, "target": { "key": "3bfa116dc8624a7b44bc4b3cd6b01f91aa9d0df525ea164f9f744a18a36b74fa" } } ], "extra": [ 1, 163, 139, 0, 142, 211, 83, 178, 203, 248, 34, 60, 19, 204, 213, 194, 140, 221, 213, 212, 230, 10, 60, 86, 226, 200, 249, 150, 71, 59, 146, 183, 59, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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