Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7af051dba672aabc5d9dc40b7b3fb2abd5f4f646da430899bfa475703e5622f1

Tx prefix hash: 53e3f7b2662cbfb83050b597e8c686631340b2dd28637bfac184cea39ae73b77
Tx public key: 79112bcf341b71131fc6aeefb0c628ef0f3a8664466a6aa398b1d3687ac75c8c
Timestamp: 1710721448 Timestamp [UCT]: 2024-03-18 00:24:08 Age [y:d:h:m:s]: 00:061:21:16:46
Block: 980654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44306 RingCT/type: yes/0
Extra: 0179112bcf341b71131fc6aeefb0c628ef0f3a8664466a6aa398b1d3687ac75c8c0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6773ae6497b1ea6f7e1b9a43d9e3ab00eb88052303d3983ec42171f4057aea79 0.600000000000 1440735 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": 980664, "vin": [ { "gen": { "height": 980654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6773ae6497b1ea6f7e1b9a43d9e3ab00eb88052303d3983ec42171f4057aea79" } } ], "extra": [ 1, 121, 17, 43, 207, 52, 27, 113, 19, 31, 198, 174, 239, 176, 198, 40, 239, 15, 58, 134, 100, 70, 106, 106, 163, 152, 177, 211, 104, 122, 199, 92, 140, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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