Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e222a5cff65219a108eeb4a5bb0c1d290b762c400d3e186aca5c6db38e21396

Tx prefix hash: be55ee7ba5f45cb8acaeec9769a666632ecd6e09e21bb52b153dd11bada4a22f
Tx public key: 0abeea08fe6829e93e29f4ddc19988d322b9c2cab01e4cff146dfc06bf1fb211
Timestamp: 1714517647 Timestamp [UCT]: 2024-04-30 22:54:07 Age [y:d:h:m:s]: 00:300:08:14:53
Block: 1012103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214667 RingCT/type: yes/0
Extra: 010abeea08fe6829e93e29f4ddc19988d322b9c2cab01e4cff146dfc06bf1fb2110211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c04b817e69944e94c4f4d3997dfbad92e47b3d613bf3341ca8612845a7eae196 0.600000000000 1474527 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": 1012113, "vin": [ { "gen": { "height": 1012103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c04b817e69944e94c4f4d3997dfbad92e47b3d613bf3341ca8612845a7eae196" } } ], "extra": [ 1, 10, 190, 234, 8, 254, 104, 41, 233, 62, 41, 244, 221, 193, 153, 136, 211, 34, 185, 194, 202, 176, 30, 76, 255, 20, 109, 252, 6, 191, 31, 178, 17, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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