Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dcc632bfcb310b9be7d3dd0ca5ebb4e8154435175dc94861864326a6000ddf0

Tx prefix hash: 5fc540e9d9c5bad27c50e9db40dc3e7f67b72c4a206f2f0a1a97e3f1cef94c04
Tx public key: d9843e798ce6a63c6b19ee1f42bfc40265319426f9f8c41e2801efbe56eac6ce
Timestamp: 1587791676 Timestamp [UCT]: 2020-04-25 05:14:36 Age [y:d:h:m:s]: 04:195:23:18:46
Block: 96092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1051467 RingCT/type: yes/0
Extra: 01d9843e798ce6a63c6b19ee1f42bfc40265319426f9f8c41e2801efbe56eac6ce0211000000268a2ee0d9000000000000000000

1 output(s) for total of 294.854717706000 dcy

stealth address amount amount idx
00: e6a41f8c2c754c6723ab0555bfaf8c5c20088e4feb72eacc06b524e8dad9be2f 294.854717706000 170515 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": 96102, "vin": [ { "gen": { "height": 96092 } } ], "vout": [ { "amount": 294854717706, "target": { "key": "e6a41f8c2c754c6723ab0555bfaf8c5c20088e4feb72eacc06b524e8dad9be2f" } } ], "extra": [ 1, 217, 132, 62, 121, 140, 230, 166, 60, 107, 25, 238, 31, 66, 191, 196, 2, 101, 49, 148, 38, 249, 248, 196, 30, 40, 1, 239, 190, 86, 234, 198, 206, 2, 17, 0, 0, 0, 38, 138, 46, 224, 217, 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