Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d8f322fe4f987b9af4ff2ccd065bf9c5963b357899f21670a9b279da5919ed9

Tx prefix hash: ee1727ff2cdcb03edcb3c59a77abc2890e674170e2f8960bd5e4368d8e6179d6
Tx public key: 705de8b4902810515029e8f581a2e147c38c6677966dcd92e3b7b2d8cf90a952
Timestamp: 1696694158 Timestamp [UCT]: 2023-10-07 15:55:58 Age [y:d:h:m:s]: 01:253:12:26:05
Block: 864541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442161 RingCT/type: yes/0
Extra: 01705de8b4902810515029e8f581a2e147c38c6677966dcd92e3b7b2d8cf90a952021100000003faf35c9c000000000000000000

1 output(s) for total of 0.838333487000 dcy

stealth address amount amount idx
00: f22ed990568f92524969d5822124ef201b98e318bf307f113306d4975f3b4cef 0.838333487000 1319057 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": 864551, "vin": [ { "gen": { "height": 864541 } } ], "vout": [ { "amount": 838333487, "target": { "key": "f22ed990568f92524969d5822124ef201b98e318bf307f113306d4975f3b4cef" } } ], "extra": [ 1, 112, 93, 232, 180, 144, 40, 16, 81, 80, 41, 232, 245, 129, 162, 225, 71, 195, 140, 102, 119, 150, 109, 205, 146, 227, 183, 178, 216, 207, 144, 169, 82, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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