Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d8ea0a660d7419a2028a27a3f4982e3e0cc99758ab0b0956a04f406b9352480

Tx prefix hash: 57c807026ef0ee33b39e7673c8d67503b55449e863d135589aecb5872b1dcb6c
Tx public key: 3eced04fe98b5ff8f0b67c95b16c1bf24ecbd3bf1cefa2aade2ccc09aec2119e
Timestamp: 1735133178 Timestamp [UCT]: 2024-12-25 13:26:18 Age [y:d:h:m:s]: 00:173:15:01:46
Block: 1182903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123802 RingCT/type: yes/0
Extra: 013eced04fe98b5ff8f0b67c95b16c1bf24ecbd3bf1cefa2aade2ccc09aec2119e0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd0a2abbe869934d5d8c01beb9210b8724c07770850bf56593655d28e0a7b536 0.600000000000 1669342 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": 1182913, "vin": [ { "gen": { "height": 1182903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd0a2abbe869934d5d8c01beb9210b8724c07770850bf56593655d28e0a7b536" } } ], "extra": [ 1, 62, 206, 208, 79, 233, 139, 95, 248, 240, 182, 124, 149, 177, 108, 27, 242, 78, 203, 211, 191, 28, 239, 162, 170, 222, 44, 204, 9, 174, 194, 17, 158, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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