Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31f0fddfce71defd5ba4c183f9966c6a7b06c31e612f69e8bf5b9301789d1c45

Tx prefix hash: a4a0e83aae75152cd927fe8f6a11f495fba5ee225429621de84bab4d4635979c
Tx public key: 78146d9e95fd582f62cd14e64bd6b388c6a53548930f1fd3edab69ce9c80040f
Timestamp: 1724375597 Timestamp [UCT]: 2024-08-23 01:13:17 Age [y:d:h:m:s]: 00:225:08:25:16
Block: 1093846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160907 RingCT/type: yes/0
Extra: 0178146d9e95fd582f62cd14e64bd6b388c6a53548930f1fd3edab69ce9c80040f021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76d38772db5bd0d401f6b060f9f87abc7e4c12b6f2d5374f953938ba7780ba67 0.600000000000 1568871 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": 1093856, "vin": [ { "gen": { "height": 1093846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76d38772db5bd0d401f6b060f9f87abc7e4c12b6f2d5374f953938ba7780ba67" } } ], "extra": [ 1, 120, 20, 109, 158, 149, 253, 88, 47, 98, 205, 20, 230, 75, 214, 179, 136, 198, 165, 53, 72, 147, 15, 31, 211, 237, 171, 105, 206, 156, 128, 4, 15, 2, 17, 0, 0, 0, 1, 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