Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c9511caf4bfd17bf5a6482ca5d4e6d4e902a5e6b1a72df9743d68a8019e829c

Tx prefix hash: 300c315002b940caa14cf60c79714824c2c7ae624ac924144de2ab647139ff3f
Tx public key: 7c34c81763471da1fddc5e89913ba5dc5419ffa0c5b21af9a3d8322af66684bc
Timestamp: 1658483797 Timestamp [UCT]: 2022-07-22 09:56:37 Age [y:d:h:m:s]: 02:275:00:18:31
Block: 549181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 717751 RingCT/type: yes/0
Extra: 017c34c81763471da1fddc5e89913ba5dc5419ffa0c5b21af9a3d8322af66684bc021100000009d3fcec30000000000000000000

1 output(s) for total of 9.296953165000 dcy

stealth address amount amount idx
00: cc6c50717036467a9558ffed878e7e15cea2ccbf282c69a185b83c7359340244 9.296953165000 980520 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": 549191, "vin": [ { "gen": { "height": 549181 } } ], "vout": [ { "amount": 9296953165, "target": { "key": "cc6c50717036467a9558ffed878e7e15cea2ccbf282c69a185b83c7359340244" } } ], "extra": [ 1, 124, 52, 200, 23, 99, 71, 29, 161, 253, 220, 94, 137, 145, 59, 165, 220, 84, 25, 255, 160, 197, 178, 26, 249, 163, 216, 50, 42, 246, 102, 132, 188, 2, 17, 0, 0, 0, 9, 211, 252, 236, 48, 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