Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 362fe4eea9e19d9653b392b1f2317a779c223abf7f86482d09ab75ac4afd457d

Tx prefix hash: 91e57a89fd6812b8206d9f154b7c106f47b87394f4c182838cc761c7f59978e4
Tx public key: a1d63d59b6583a96e8e11dc88c1fd006728e1caf03ed81ca95f3d9a6e8e8d83e
Timestamp: 1577567963 Timestamp [UCT]: 2019-12-28 21:19:23 Age [y:d:h:m:s]: 05:110:13:53:26
Block: 33848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1228823 RingCT/type: yes/0
Extra: 01a1d63d59b6583a96e8e11dc88c1fd006728e1caf03ed81ca95f3d9a6e8e8d83e0211000000124ac5aa02000000000000000000

1 output(s) for total of 474.092819595000 dcy

stealth address amount amount idx
00: 58fe1915798eba38f962c5dfcab24ce0d80bd3bac6605a8718572dbc8b58d78f 474.092819595000 56806 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": 33858, "vin": [ { "gen": { "height": 33848 } } ], "vout": [ { "amount": 474092819595, "target": { "key": "58fe1915798eba38f962c5dfcab24ce0d80bd3bac6605a8718572dbc8b58d78f" } } ], "extra": [ 1, 161, 214, 61, 89, 182, 88, 58, 150, 232, 225, 29, 200, 140, 31, 208, 6, 114, 142, 28, 175, 3, 237, 129, 202, 149, 243, 217, 166, 232, 232, 216, 62, 2, 17, 0, 0, 0, 18, 74, 197, 170, 2, 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