Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1b77083faf36eb6021de4392ffe65d1fa8a8d1ac19bd3e93a7c9c8151a7af5

Tx prefix hash: 158cb94c943e63432eeffcd8551857cd11167d8c18fe08158039cdea528b0870
Tx public key: 34df28e08dcb83fdd232be0c4e360f3ab2be1c0bf94875378ec83dca942eacba
Timestamp: 1700340705 Timestamp [UCT]: 2023-11-18 20:51:45 Age [y:d:h:m:s]: 01:150:04:38:16
Block: 894571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368529 RingCT/type: yes/0
Extra: 0134df28e08dcb83fdd232be0c4e360f3ab2be1c0bf94875378ec83dca942eacba021100000002faf35c9c000000000000000000

1 output(s) for total of 0.666676143000 dcy

stealth address amount amount idx
00: ad736855169d10e00d0ace3ca45d3ef954fd88b0f3a4960cc4ba2788c13fb810 0.666676143000 1350774 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": 894581, "vin": [ { "gen": { "height": 894571 } } ], "vout": [ { "amount": 666676143, "target": { "key": "ad736855169d10e00d0ace3ca45d3ef954fd88b0f3a4960cc4ba2788c13fb810" } } ], "extra": [ 1, 52, 223, 40, 224, 141, 203, 131, 253, 210, 50, 190, 12, 78, 54, 15, 58, 178, 190, 28, 11, 249, 72, 117, 55, 142, 200, 61, 202, 148, 46, 172, 186, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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