Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79eef1ccb12cee728429b88d6479197744c5b4904e460b1bef758dab6bdb5f67

Tx prefix hash: 4b6c7eb3f7a90ea290a372c13329155cccd5a12bcce18176b78963c5b393cfc4
Tx public key: 3f8f59458307b3a9a282be1b72547e15269293ad6b791bbca3fc0b34406e8253
Timestamp: 1722204495 Timestamp [UCT]: 2024-07-28 22:08:15 Age [y:d:h:m:s]: 00:306:14:18:59
Block: 1075824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219094 RingCT/type: yes/0
Extra: 013f8f59458307b3a9a282be1b72547e15269293ad6b791bbca3fc0b34406e8253021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36c50b30289c0d64fd8d5f4dc18636951e81ae21ec4352acb60a99d470cf3946 0.600000000000 1548355 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": 1075834, "vin": [ { "gen": { "height": 1075824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36c50b30289c0d64fd8d5f4dc18636951e81ae21ec4352acb60a99d470cf3946" } } ], "extra": [ 1, 63, 143, 89, 69, 131, 7, 179, 169, 162, 130, 190, 27, 114, 84, 126, 21, 38, 146, 147, 173, 107, 121, 27, 188, 163, 252, 11, 52, 64, 110, 130, 83, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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