Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2a155a954bcd8062ece0382ead5d1a9949624c88318ad0175439bef36e6219d

Tx prefix hash: 83bd7d5b0309b346c44bd362eb03c7a4bdb59f23650f17cdfd224f1dce65d2c6
Tx public key: d661d52ee601a95c65e8e37d38c1e6f806a1a7f0989001964ca007b5a52a4267
Timestamp: 1709620154 Timestamp [UCT]: 2024-03-05 06:29:14 Age [y:d:h:m:s]: 00:357:18:10:07
Block: 971507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255786 RingCT/type: yes/0
Extra: 01d661d52ee601a95c65e8e37d38c1e6f806a1a7f0989001964ca007b5a52a42670211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77651c95aedef4b8b14ae41bbc78863cd2d9487c5650d5936291cac6b61841cc 0.600000000000 1431404 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": 971517, "vin": [ { "gen": { "height": 971507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77651c95aedef4b8b14ae41bbc78863cd2d9487c5650d5936291cac6b61841cc" } } ], "extra": [ 1, 214, 97, 213, 46, 230, 1, 169, 92, 101, 232, 227, 125, 56, 193, 230, 248, 6, 161, 167, 240, 152, 144, 1, 150, 76, 160, 7, 181, 165, 42, 66, 103, 2, 17, 0, 0, 0, 6, 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