Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e9fefffa6e3d6947e0dfc6dc6a0d7a5f437be2ab40869ea24b827fa369e203a

Tx prefix hash: 8b3ea4e80daf472a8593feb99cd99a150be746aa81cd497d837f931573539d29
Tx public key: d3c8a83656e40ce7a47e0a6897c558ec6440822622e60d6f8e67839d9fdb20fe
Timestamp: 1705188471 Timestamp [UCT]: 2024-01-13 23:27:51 Age [y:d:h:m:s]: 01:085:21:43:21
Block: 934747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322492 RingCT/type: yes/0
Extra: 01d3c8a83656e40ce7a47e0a6897c558ec6440822622e60d6f8e67839d9fdb20fe0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b360b09c388808fe42027eda2a68ea6a8bacf21f1541b9c1193d0aecfdc3d239 0.600000000000 1392763 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": 934757, "vin": [ { "gen": { "height": 934747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b360b09c388808fe42027eda2a68ea6a8bacf21f1541b9c1193d0aecfdc3d239" } } ], "extra": [ 1, 211, 200, 168, 54, 86, 228, 12, 231, 164, 126, 10, 104, 151, 197, 88, 236, 100, 64, 130, 38, 34, 230, 13, 111, 142, 103, 131, 157, 159, 219, 32, 254, 2, 17, 0, 0, 0, 2, 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