Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99821bc7e4736d97061fb7ed9d1a1d263fb0896f46610302d4a01c62f51325b2

Tx prefix hash: d22e8fafeb8c9fa30aebf04cc4c01b66e91bb7490d01bdaf765276a49029b732
Tx public key: d3ee4ccb54404314203d099d980fee8d3bfad26974e523d582c88d935f61179b
Timestamp: 1733914945 Timestamp [UCT]: 2024-12-11 11:02:25 Age [y:d:h:m:s]: 00:105:09:36:19
Block: 1172822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75087 RingCT/type: yes/0
Extra: 01d3ee4ccb54404314203d099d980fee8d3bfad26974e523d582c88d935f61179b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17fe807a0cf324b5c84950b737639cb63c2ca14f1a395b985e9e5ee866531780 0.600000000000 1658761 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": 1172832, "vin": [ { "gen": { "height": 1172822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17fe807a0cf324b5c84950b737639cb63c2ca14f1a395b985e9e5ee866531780" } } ], "extra": [ 1, 211, 238, 76, 203, 84, 64, 67, 20, 32, 61, 9, 157, 152, 15, 238, 141, 59, 250, 210, 105, 116, 229, 35, 213, 130, 200, 141, 147, 95, 97, 23, 155, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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