Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a76c0e035df29304ad4aa7fcd227a7ab777807bbc81c175b3aacef5832c15782

Tx prefix hash: 41ad401c79b3c68c86f8eb1c5a5c25943439ab2592c94571eb2f59cde1f07e60
Tx public key: a6518be6c9e7edeafedb5b2675f6b1a328b2ffb6de8b6826ef22829b78b4f19d
Timestamp: 1705924310 Timestamp [UCT]: 2024-01-22 11:51:50 Age [y:d:h:m:s]: 01:286:19:11:09
Block: 940825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 463800 RingCT/type: yes/0
Extra: 01a6518be6c9e7edeafedb5b2675f6b1a328b2ffb6de8b6826ef22829b78b4f19d0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbecdcc88e23443a8e1789ae01acd484aefb1e984f512b6452f85d529cb5a389 0.600000000000 1398965 of 15

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": 940835, "vin": [ { "gen": { "height": 940825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbecdcc88e23443a8e1789ae01acd484aefb1e984f512b6452f85d529cb5a389" } } ], "extra": [ 1, 166, 81, 139, 230, 201, 231, 237, 234, 254, 219, 91, 38, 117, 246, 177, 163, 40, 178, 255, 182, 222, 139, 104, 38, 239, 34, 130, 155, 120, 180, 241, 157, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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