Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea9bbe39f3d99eb0e9981d65364c17bb075039bac0b2b45760aca742c60ca5e5

Tx prefix hash: fec2f0f3fd553d4c746c6c76a3428273fab2fb6a438682a394c9a49b76e26aa3
Tx public key: c76aeb3c2ccdae397070d377eb08c47e5fa59c46c09767b55051c51a969ceb62
Timestamp: 1699871064 Timestamp [UCT]: 2023-11-13 10:24:24 Age [y:d:h:m:s]: 01:145:01:29:38
Block: 890686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364849 RingCT/type: yes/0
Extra: 01c76aeb3c2ccdae397070d377eb08c47e5fa59c46c09767b55051c51a969ceb6202110000000375e3f0e9000000000000000000

1 output(s) for total of 0.686732400000 dcy

stealth address amount amount idx
00: 95d2b235e8b1cee8319ef759ea032f98bb3dcaf1a5671e64d9eebe00ed873836 0.686732400000 1346715 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": 890696, "vin": [ { "gen": { "height": 890686 } } ], "vout": [ { "amount": 686732400, "target": { "key": "95d2b235e8b1cee8319ef759ea032f98bb3dcaf1a5671e64d9eebe00ed873836" } } ], "extra": [ 1, 199, 106, 235, 60, 44, 205, 174, 57, 112, 112, 211, 119, 235, 8, 196, 126, 95, 165, 156, 70, 192, 151, 103, 181, 80, 81, 197, 26, 150, 156, 235, 98, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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