Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a9c9b812d5ac2161db57c0af7eda31de0fc2bc6f4817dd794b26422b873f31d

Tx prefix hash: 3e4ce629d22d963714a5ef5ca869245bc97736f66aea40a527350e470d12e9b2
Tx public key: 9c59945599ac99d24edea832a0788994c5079b74eac0d9d7065afc3876f4815a
Timestamp: 1712698071 Timestamp [UCT]: 2024-04-09 21:27:51 Age [y:d:h:m:s]: 00:314:04:20:54
Block: 996998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224593 RingCT/type: yes/0
Extra: 019c59945599ac99d24edea832a0788994c5079b74eac0d9d7065afc3876f4815a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00a44f541a159b501e578b9b77e4b6d55abafd23f6ae214919e89d3cbd3663fd 0.600000000000 1457426 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": 997008, "vin": [ { "gen": { "height": 996998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00a44f541a159b501e578b9b77e4b6d55abafd23f6ae214919e89d3cbd3663fd" } } ], "extra": [ 1, 156, 89, 148, 85, 153, 172, 153, 210, 78, 222, 168, 50, 160, 120, 137, 148, 197, 7, 155, 116, 234, 192, 217, 215, 6, 90, 252, 56, 118, 244, 129, 90, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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