Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08f1f5280e9b3780a114609a6d321daa46aba6c4c744ad4a1bc34b12f3d6273a

Tx prefix hash: e8a7885692f375c44c84e6a0637cc78207485b1038c1ff14074df40a341fe634
Tx public key: c91e44981747d39f5c2bb6ff8f3b5a92eb6113a9980214cd6181cb1ed3b18202
Timestamp: 1735215718 Timestamp [UCT]: 2024-12-26 12:21:58 Age [y:d:h:m:s]: 00:095:16:00:06
Block: 1183591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68140 RingCT/type: yes/0
Extra: 01c91e44981747d39f5c2bb6ff8f3b5a92eb6113a9980214cd6181cb1ed3b1820202110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0eaa49d4ebf21ccfe599c251d4b57bbc4734f65b386bf609b7f4daf054d8fad 0.600000000000 1670036 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": 1183601, "vin": [ { "gen": { "height": 1183591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0eaa49d4ebf21ccfe599c251d4b57bbc4734f65b386bf609b7f4daf054d8fad" } } ], "extra": [ 1, 201, 30, 68, 152, 23, 71, 211, 159, 92, 43, 182, 255, 143, 59, 90, 146, 235, 97, 19, 169, 152, 2, 20, 205, 97, 129, 203, 30, 211, 177, 130, 2, 2, 17, 0, 0, 0, 15, 31, 10, 83, 235, 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