Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 352f189c816fadeaf536692cedc8ebbc1800c4e70dfb7fbd8eff773009ca541d

Tx prefix hash: a38f2b996edac5cf57c2e8d34641baf2087eafa4ba12cd1096c576dd7a4cd647
Tx public key: 887f6250d9c11b47c24aed04cf014f9ea1594e70a1b680f9ad28047c1cbf91e9
Timestamp: 1731424140 Timestamp [UCT]: 2024-11-12 15:09:00 Age [y:d:h:m:s]: 00:137:12:22:35
Block: 1152173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98108 RingCT/type: yes/0
Extra: 01887f6250d9c11b47c24aed04cf014f9ea1594e70a1b680f9ad28047c1cbf91e90211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68daa035002dcf367b69d3fa77e852ad4c5a2e70111218d81f70d5012f033ec7 0.600000000000 1637764 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": 1152183, "vin": [ { "gen": { "height": 1152173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68daa035002dcf367b69d3fa77e852ad4c5a2e70111218d81f70d5012f033ec7" } } ], "extra": [ 1, 136, 127, 98, 80, 217, 193, 27, 71, 194, 74, 237, 4, 207, 1, 79, 158, 161, 89, 78, 112, 161, 182, 128, 249, 173, 40, 4, 124, 28, 191, 145, 233, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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