Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08689bc2695c0465fc4977f8b1f1b6e1e81d08b3034081ea1af1c400632cea03

Tx prefix hash: c7c444c1b18a7e0810bac597d897b6fae5905bab49151850add15c754d215a53
Tx public key: dce0b1be732276997a63d6b22680d8f39a6db399726852d0f293b93baeb27310
Timestamp: 1694264736 Timestamp [UCT]: 2023-09-09 13:05:36 Age [y:d:h:m:s]: 01:210:09:08:17
Block: 844378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411451 RingCT/type: yes/0
Extra: 01dce0b1be732276997a63d6b22680d8f39a6db399726852d0f293b93baeb273100211000000084b8f5122000000000000000000

1 output(s) for total of 0.977744165000 dcy

stealth address amount amount idx
00: 747093d8d650370123a80c7f5c98bb0b0572b3bb9571d7a3d3b2847f4335c61e 0.977744165000 1297682 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": 844388, "vin": [ { "gen": { "height": 844378 } } ], "vout": [ { "amount": 977744165, "target": { "key": "747093d8d650370123a80c7f5c98bb0b0572b3bb9571d7a3d3b2847f4335c61e" } } ], "extra": [ 1, 220, 224, 177, 190, 115, 34, 118, 153, 122, 99, 214, 178, 38, 128, 216, 243, 154, 109, 179, 153, 114, 104, 82, 208, 242, 147, 185, 59, 174, 178, 115, 16, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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