Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 040da228c3a41dcc5e4c19df8d4175a8db81df3c906ee53582880fb66417ebe7

Tx prefix hash: ee2a780ea6f6d14576bfb48c943c5c6873903e89bdc082f9ec3534efb9691c39
Tx public key: 3b60ad33c80b118ecf6f89a0ea63c15b3e563e1aeefb7d09dcffd42fcc61baff
Timestamp: 1713597330 Timestamp [UCT]: 2024-04-20 07:15:30 Age [y:d:h:m:s]: 00:310:23:02:36
Block: 1004451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222292 RingCT/type: yes/0
Extra: 013b60ad33c80b118ecf6f89a0ea63c15b3e563e1aeefb7d09dcffd42fcc61baff0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c9f5beb59b72e3f19148e3608cd25e0edf42f502b5c5f1738eec78d291326fe 0.600000000000 1465019 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": 1004461, "vin": [ { "gen": { "height": 1004451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c9f5beb59b72e3f19148e3608cd25e0edf42f502b5c5f1738eec78d291326fe" } } ], "extra": [ 1, 59, 96, 173, 51, 200, 11, 17, 142, 207, 111, 137, 160, 234, 99, 193, 91, 62, 86, 62, 26, 238, 251, 125, 9, 220, 255, 212, 47, 204, 97, 186, 255, 2, 17, 0, 0, 0, 4, 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