Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f95fec98f880d34069a7527b2bd731c36f59f7dce947b9b2084a45e53dca0811

Tx prefix hash: 2e2c2c2677855e28875b16e041ae80ea425bf67765068d0720e15f55607f9bb2
Tx public key: 0e215a0acaf17c233b3dcda12f7fcce41995f751e1f44e3e9f53333ad27589fe
Timestamp: 1714018841 Timestamp [UCT]: 2024-04-25 04:20:41 Age [y:d:h:m:s]: 00:362:21:33:34
Block: 1007959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259433 RingCT/type: yes/0
Extra: 010e215a0acaf17c233b3dcda12f7fcce41995f751e1f44e3e9f53333ad27589fe0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa83a04d3d1636887f4f397fccf5b8d93a132f71d9f9e6260b7dd3a987d58481 0.600000000000 1469425 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": 1007969, "vin": [ { "gen": { "height": 1007959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa83a04d3d1636887f4f397fccf5b8d93a132f71d9f9e6260b7dd3a987d58481" } } ], "extra": [ 1, 14, 33, 90, 10, 202, 241, 124, 35, 59, 61, 205, 161, 47, 127, 204, 228, 25, 149, 247, 81, 225, 244, 78, 62, 159, 83, 51, 58, 210, 117, 137, 254, 2, 17, 0, 0, 0, 5, 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