Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e174742e616cb9b4974b0db69a963a0e0b83fb1688f1bc726a64eaae3f7ee4b

Tx prefix hash: 4841ce5d46b9d7945f9baf08aeb270cd78ca76ebb477bb70b9d399fbd730597e
Tx public key: 4e03034b5cb32d5a7fe628bbbfa44659605ca6541fbfbcef6fb647f2b1bc46e7
Timestamp: 1719954889 Timestamp [UCT]: 2024-07-02 21:14:49 Age [y:d:h:m:s]: 00:255:03:40:50
Block: 1057173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182324 RingCT/type: yes/0
Extra: 014e03034b5cb32d5a7fe628bbbfa44659605ca6541fbfbcef6fb647f2b1bc46e70211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01c7b332408d9aa810796baedd1cc566561eb46db6d15d01d1099bb3004d7939 0.600000000000 1527606 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": 1057183, "vin": [ { "gen": { "height": 1057173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01c7b332408d9aa810796baedd1cc566561eb46db6d15d01d1099bb3004d7939" } } ], "extra": [ 1, 78, 3, 3, 75, 92, 179, 45, 90, 127, 230, 40, 187, 191, 164, 70, 89, 96, 92, 166, 84, 31, 191, 188, 239, 111, 182, 71, 242, 177, 188, 70, 231, 2, 17, 0, 0, 0, 1, 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