Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14ca0fc09bfa1ab82801b5ac3d03503f3bd24515a8aa4017aded877b32724b8c

Tx prefix hash: e6d816ce908a823ef1b81ebf04522875934cee9081390f705fca8d29f5329b13
Tx public key: f34db286d9b719222c21673bc00caf12ffa935250dd31ab5e9826ed43028dc8f
Timestamp: 1734908158 Timestamp [UCT]: 2024-12-22 22:55:58 Age [y:d:h:m:s]: 00:326:16:11:16
Block: 1181064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230957 RingCT/type: yes/0
Extra: 01f34db286d9b719222c21673bc00caf12ffa935250dd31ab5e9826ed43028dc8f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2762f0cb37670818e93b4c9e7f1d4f0b2666b9c0b373ac958220504c2e4fa882 0.600000000000 1667479 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": 1181074, "vin": [ { "gen": { "height": 1181064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2762f0cb37670818e93b4c9e7f1d4f0b2666b9c0b373ac958220504c2e4fa882" } } ], "extra": [ 1, 243, 77, 178, 134, 217, 183, 25, 34, 44, 33, 103, 59, 192, 12, 175, 18, 255, 169, 53, 37, 13, 211, 26, 181, 233, 130, 110, 212, 48, 40, 220, 143, 2, 17, 0, 0, 0, 4, 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