Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b22d8eacdafeddaec1f38ab4e92ea8e05bd5115ca6d4de8e684c8deb2bc5be84

Tx prefix hash: d30061096251ac4f7e4e186c6025305ccbf4a4559993007f45595258914abb01
Tx public key: 453ae98ba78854e98e55686c1820def7eb5c7b3c7bd64b0a2fa58dc14e6aa6b1
Timestamp: 1714199022 Timestamp [UCT]: 2024-04-27 06:23:42 Age [y:d:h:m:s]: 00:354:13:07:21
Block: 1009454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253462 RingCT/type: yes/0
Extra: 01453ae98ba78854e98e55686c1820def7eb5c7b3c7bd64b0a2fa58dc14e6aa6b102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc1f4b89108e5c2791bb1fa43b03ae97f40dd24c47271fa88212678435025121 0.600000000000 1471132 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": 1009464, "vin": [ { "gen": { "height": 1009454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc1f4b89108e5c2791bb1fa43b03ae97f40dd24c47271fa88212678435025121" } } ], "extra": [ 1, 69, 58, 233, 139, 167, 136, 84, 233, 142, 85, 104, 108, 24, 32, 222, 247, 235, 92, 123, 60, 123, 214, 75, 10, 47, 165, 141, 193, 78, 106, 166, 177, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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