Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c119710b01df2b09c5646eb725e2be5413a59e35661f3145a823875f8d65542

Tx prefix hash: ceb3c6f4aad9b8950deefa68fe83888f62c4dccdf8cbbcf78694986b0868a154
Tx public key: e8ea1e43f6a5fb6cd21e9be61380a1ed2e3630ce7fa98c894ba4d2ca1a8e8378
Timestamp: 1693387125 Timestamp [UCT]: 2023-08-30 09:18:45 Age [y:d:h:m:s]: 01:179:00:03:18
Block: 837100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389022 RingCT/type: yes/0
Extra: 01e8ea1e43f6a5fb6cd21e9be61380a1ed2e3630ce7fa98c894ba4d2ca1a8e837802110000000ad4dbf7b9000000000000000000

1 output(s) for total of 1.033570913000 dcy

stealth address amount amount idx
00: 792e5737a4b7ac6ec602e301d69919cfddb72d1723fc12f2d1207367d0d2bd0e 1.033570913000 1289712 of 0

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": 837110, "vin": [ { "gen": { "height": 837100 } } ], "vout": [ { "amount": 1033570913, "target": { "key": "792e5737a4b7ac6ec602e301d69919cfddb72d1723fc12f2d1207367d0d2bd0e" } } ], "extra": [ 1, 232, 234, 30, 67, 246, 165, 251, 108, 210, 30, 155, 230, 19, 128, 161, 237, 46, 54, 48, 206, 127, 169, 140, 137, 75, 164, 210, 202, 26, 142, 131, 120, 2, 17, 0, 0, 0, 10, 212, 219, 247, 185, 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