Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 030ffccaa00be38c07791f8c139deb3d4ca511c6d451a181881e748400299263

Tx prefix hash: 8cce25d3c0ea0266f78ef34b1b722c196a049a066155a9ebcf44f8e3d08cdcda
Tx public key: 86d0003d45cf153493c79eb05b0d34a2fce360898b6fdb7b58bc50a8bedfa6a5
Timestamp: 1702418342 Timestamp [UCT]: 2023-12-12 21:59:02 Age [y:d:h:m:s]: 01:145:12:20:28
Block: 911815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365134 RingCT/type: yes/0
Extra: 0186d0003d45cf153493c79eb05b0d34a2fce360898b6fdb7b58bc50a8bedfa6a502110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ada9b59405de65659e9a77e6dd323a11b254dc4bcdfefb4f3f1d24554211bf4 0.600000000000 1369031 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": 911825, "vin": [ { "gen": { "height": 911815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ada9b59405de65659e9a77e6dd323a11b254dc4bcdfefb4f3f1d24554211bf4" } } ], "extra": [ 1, 134, 208, 0, 61, 69, 207, 21, 52, 147, 199, 158, 176, 91, 13, 52, 162, 252, 227, 96, 137, 139, 111, 219, 123, 88, 188, 80, 168, 190, 223, 166, 165, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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