Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfec0253699915d0f31f655f44577f4f3951f73f6eebe49a44782affc3696890

Tx prefix hash: 2337a95b560c26bda60f860f0b97c03ec2b73cd4742a7e49ee9055fd7dad830d
Tx public key: a2dbe63ae50be81d158d79300c0bc7ffdd4eb11bf69f13d55ee2b39f3f50bd9f
Timestamp: 1697006652 Timestamp [UCT]: 2023-10-11 06:44:12 Age [y:d:h:m:s]: 01:094:18:56:43
Block: 867130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329000 RingCT/type: yes/0
Extra: 01a2dbe63ae50be81d158d79300c0bc7ffdd4eb11bf69f13d55ee2b39f3f50bd9f0211000000014b8f5122000000000000000000

1 output(s) for total of 0.821936712000 dcy

stealth address amount amount idx
00: c36e0fb665efa150fabe013541d3270e3b4ec6975e257abcbd9492e85b1aa023 0.821936712000 1321786 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": 867140, "vin": [ { "gen": { "height": 867130 } } ], "vout": [ { "amount": 821936712, "target": { "key": "c36e0fb665efa150fabe013541d3270e3b4ec6975e257abcbd9492e85b1aa023" } } ], "extra": [ 1, 162, 219, 230, 58, 229, 11, 232, 29, 21, 141, 121, 48, 12, 11, 199, 255, 221, 78, 177, 27, 246, 159, 19, 213, 94, 226, 179, 159, 63, 80, 189, 159, 2, 17, 0, 0, 0, 1, 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