Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80c04539447f36f54ad08bc1995e447f872cc4d75e2f755f0c128a02fc6d462f

Tx prefix hash: 398f2983324f016e28dbcb06c9777efad3d67004e3ca30ba179b0cbaba008efd
Tx public key: e4a9e1b2e4a9a4b323631476e15599b8cf225b0d8a3177a47f599e128edcab25
Timestamp: 1716448365 Timestamp [UCT]: 2024-05-23 07:12:45 Age [y:d:h:m:s]: 00:303:17:25:21
Block: 1028115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217073 RingCT/type: yes/0
Extra: 01e4a9e1b2e4a9a4b323631476e15599b8cf225b0d8a3177a47f599e128edcab25021100000001e08532b6000000000000000000

1 output(s) for total of 0.615590000000 dcy

stealth address amount amount idx
00: 2ee8bc113d22c45b6d268707ef7759011241a05264fa61574fc3a98bb3f5b3b1 0.615590000000 1496044 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": 1028125, "vin": [ { "gen": { "height": 1028115 } } ], "vout": [ { "amount": 615590000, "target": { "key": "2ee8bc113d22c45b6d268707ef7759011241a05264fa61574fc3a98bb3f5b3b1" } } ], "extra": [ 1, 228, 169, 225, 178, 228, 169, 164, 179, 35, 99, 20, 118, 225, 85, 153, 184, 207, 34, 91, 13, 138, 49, 119, 164, 127, 89, 158, 18, 142, 220, 171, 37, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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