Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e40fa7dd328ee4794107ef4e5d31e99fb69d70c660bc0b26621dded4a8ee4d66

Tx prefix hash: 4e8b78b5fdd87897701234fcba9d3dbfee706a830e930a1b63e6e380e1570be5
Tx public key: 1168abf64a10298710065c99a54a918b3928e5f87159c67e3bb12ca5bfb17adf
Timestamp: 1696749655 Timestamp [UCT]: 2023-10-08 07:20:55 Age [y:d:h:m:s]: 01:115:15:24:11
Block: 865005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343648 RingCT/type: yes/0
Extra: 011168abf64a10298710065c99a54a918b3928e5f87159c67e3bb12ca5bfb17adf021100000001bfa22221000000000000000000

1 output(s) for total of 0.835370989000 dcy

stealth address amount amount idx
00: 9a651ba72ae42a41110f1eb0b06b11df24fe5d4d2fca97b3a0d0eda2dcdd2492 0.835370989000 1319531 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": 865015, "vin": [ { "gen": { "height": 865005 } } ], "vout": [ { "amount": 835370989, "target": { "key": "9a651ba72ae42a41110f1eb0b06b11df24fe5d4d2fca97b3a0d0eda2dcdd2492" } } ], "extra": [ 1, 17, 104, 171, 246, 74, 16, 41, 135, 16, 6, 92, 153, 165, 74, 145, 139, 57, 40, 229, 248, 113, 89, 198, 126, 59, 177, 44, 165, 191, 177, 122, 223, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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