Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf7c64a338e0c968f0ff3db972cec38d1f9a3169d6630aba8c5e91ac1fee7eb4

Tx prefix hash: b91ef90b56170c41a7ff8576448744faa6d756ba0e0b85c963e68be378308f85
Tx public key: 4465dc14abe9323bcdba5528cb38eb1c9dde3cbfeeff3c447f087e1c1df1c347
Timestamp: 1726516929 Timestamp [UCT]: 2024-09-16 20:02:09 Age [y:d:h:m:s]: 00:273:08:51:43
Block: 1111581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195146 RingCT/type: yes/0
Extra: 014465dc14abe9323bcdba5528cb38eb1c9dde3cbfeeff3c447f087e1c1df1c34702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af8fb4d0b919d0e0e18995e05d0d2243cff5e977220c07c62b1aac1491deed67 0.600000000000 1590594 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": 1111591, "vin": [ { "gen": { "height": 1111581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af8fb4d0b919d0e0e18995e05d0d2243cff5e977220c07c62b1aac1491deed67" } } ], "extra": [ 1, 68, 101, 220, 20, 171, 233, 50, 59, 205, 186, 85, 40, 203, 56, 235, 28, 157, 222, 60, 191, 238, 255, 60, 68, 127, 8, 126, 28, 29, 241, 195, 71, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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