Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 118c49f428f4f7dfd42482693d5997be200b03225e62cc69cddc94b128e068d4

Tx prefix hash: 4dbc8b0c177a0ab1909101b0a59a787c75dd1ce014f3287d66f979a25e941a03
Tx public key: fde23cab48b879a18f672a223d039b6db8cf4c321809cb99e3f77e9cec99bc10
Timestamp: 1709379620 Timestamp [UCT]: 2024-03-02 11:40:20 Age [y:d:h:m:s]: 01:093:18:08:26
Block: 969514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328059 RingCT/type: yes/0
Extra: 01fde23cab48b879a18f672a223d039b6db8cf4c321809cb99e3f77e9cec99bc100211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38834db7ec5e7f95557160fdaa083ec33f7d12574071fa053d6904a1f9e962d5 0.600000000000 1429347 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": 969524, "vin": [ { "gen": { "height": 969514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38834db7ec5e7f95557160fdaa083ec33f7d12574071fa053d6904a1f9e962d5" } } ], "extra": [ 1, 253, 226, 60, 171, 72, 184, 121, 161, 143, 103, 42, 34, 61, 3, 155, 109, 184, 207, 76, 50, 24, 9, 203, 153, 227, 247, 126, 156, 236, 153, 188, 16, 2, 17, 0, 0, 0, 2, 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