Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4315b4bbdf0b0fe3b43f246d8c5c2a212ffecd04accb98be8af9e9951a1588c

Tx prefix hash: 67410a9056717764a97ab903a3a4811bd03d1e557f34eec268c852437e44e186
Tx public key: ae9593437b49e68e60cc5b14780905dfa91ec69b35b6cf1032ef3c5f248d2ec5
Timestamp: 1715643214 Timestamp [UCT]: 2024-05-13 23:33:34 Age [y:d:h:m:s]: 00:351:15:21:04
Block: 1021432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251359 RingCT/type: yes/0
Extra: 01ae9593437b49e68e60cc5b14780905dfa91ec69b35b6cf1032ef3c5f248d2ec50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 755f4cb001194d38b4e3d01ac885a49c72dcdd269657669d2098a38029fd1bdc 0.600000000000 1485749 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": 1021442, "vin": [ { "gen": { "height": 1021432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "755f4cb001194d38b4e3d01ac885a49c72dcdd269657669d2098a38029fd1bdc" } } ], "extra": [ 1, 174, 149, 147, 67, 123, 73, 230, 142, 96, 204, 91, 20, 120, 9, 5, 223, 169, 30, 198, 155, 53, 182, 207, 16, 50, 239, 60, 95, 36, 141, 46, 197, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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