Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cdb3602704be19224f769b54c36938e7d96bcab1cd9a3db1b92120ab6fec14d

Tx prefix hash: 45f858ba6b6a43ac4d5c76237b5b8822e467e8f4a606202a299f8a0207380d44
Tx public key: fe557c5b0014e4b4478e78641a713891c2c3e36b47cdfc545832c6e8b27b5ee0
Timestamp: 1703220368 Timestamp [UCT]: 2023-12-22 04:46:08 Age [y:d:h:m:s]: 01:317:20:24:24
Block: 918440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486010 RingCT/type: yes/0
Extra: 01fe557c5b0014e4b4478e78641a713891c2c3e36b47cdfc545832c6e8b27b5ee00211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0db7d8dcdd62998235ee1adae6ff343230692faf8754c8f969a6401712d4db7f 0.600000000000 1376084 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": 918450, "vin": [ { "gen": { "height": 918440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0db7d8dcdd62998235ee1adae6ff343230692faf8754c8f969a6401712d4db7f" } } ], "extra": [ 1, 254, 85, 124, 91, 0, 20, 228, 180, 71, 142, 120, 100, 26, 113, 56, 145, 194, 195, 227, 107, 71, 205, 252, 84, 88, 50, 198, 232, 178, 123, 94, 224, 2, 17, 0, 0, 0, 4, 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