Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6fb05894a5395e0a0c789b158e718fb411183644b3c2937575b59ea3e3271f0

Tx prefix hash: b9f5133727e48fde084645455801a16ff867fa48eeae9487a72468ee4cc81dbb
Tx public key: af1b99cabcc3dc3b1f0c87e94d694a23298e36a7c48875e543666c679f9adeb5
Timestamp: 1703876808 Timestamp [UCT]: 2023-12-29 19:06:48 Age [y:d:h:m:s]: 01:312:20:36:07
Block: 923883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482413 RingCT/type: yes/0
Extra: 01af1b99cabcc3dc3b1f0c87e94d694a23298e36a7c48875e543666c679f9adeb502110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 146d9f910f65f27c6438ac6b982727753ca0051e0e7f1a17bf17f957f077dcab 0.600000000000 1381621 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": 923893, "vin": [ { "gen": { "height": 923883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "146d9f910f65f27c6438ac6b982727753ca0051e0e7f1a17bf17f957f077dcab" } } ], "extra": [ 1, 175, 27, 153, 202, 188, 195, 220, 59, 31, 12, 135, 233, 77, 105, 74, 35, 41, 142, 54, 167, 196, 136, 117, 229, 67, 102, 108, 103, 159, 154, 222, 181, 2, 17, 0, 0, 0, 13, 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