Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 020fee2e9434028d232b6211d284ac2aa70c72caca8d5cf6db381ed1bcaff22c

Tx prefix hash: c7cabf797dd9328cde2a139381ee27a2c25587c2d38d6179d34f85c93b942145
Tx public key: a02320f2b197fec3585d83ae4c7a74cf01eea64e5c466579a66624d2baa40f58
Timestamp: 1731718469 Timestamp [UCT]: 2024-11-16 00:54:29 Age [y:d:h:m:s]: 00:194:05:54:04
Block: 1154622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138696 RingCT/type: yes/0
Extra: 01a02320f2b197fec3585d83ae4c7a74cf01eea64e5c466579a66624d2baa40f580211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e75749d42fd504e5d6024b72a0a1a1c7c55a347accde2fe28c57c4270d0fd99 0.600000000000 1640235 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": 1154632, "vin": [ { "gen": { "height": 1154622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e75749d42fd504e5d6024b72a0a1a1c7c55a347accde2fe28c57c4270d0fd99" } } ], "extra": [ 1, 160, 35, 32, 242, 177, 151, 254, 195, 88, 93, 131, 174, 76, 122, 116, 207, 1, 238, 166, 78, 92, 70, 101, 121, 166, 102, 36, 210, 186, 164, 15, 88, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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