Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6a443932e9ad1fe1a5af564d0f8bd6be9e032d1780025e397efb700ab14cedf

Tx prefix hash: dffee3ecd720ccd8e1d59c114ed751d21339b744f5c97c005a259bdd73fe9911
Tx public key: fe5df78c2eeb5d678e12730c8646009267f6d3537dc4f74e6a9409d3f5843b69
Timestamp: 1698237844 Timestamp [UCT]: 2023-10-25 12:44:04 Age [y:d:h:m:s]: 01:204:00:52:09
Block: 877356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406845 RingCT/type: yes/0
Extra: 01fe5df78c2eeb5d678e12730c8646009267f6d3537dc4f74e6a9409d3f5843b6902110000000233af99f4000000000000000000

1 output(s) for total of 0.760248165000 dcy

stealth address amount amount idx
00: 653fc3e6a4d40648eaaab9dedef7dd21cdf188e39872e8372bbff02dee550125 0.760248165000 1332730 of 0

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": 877366, "vin": [ { "gen": { "height": 877356 } } ], "vout": [ { "amount": 760248165, "target": { "key": "653fc3e6a4d40648eaaab9dedef7dd21cdf188e39872e8372bbff02dee550125" } } ], "extra": [ 1, 254, 93, 247, 140, 46, 235, 93, 103, 142, 18, 115, 12, 134, 70, 0, 146, 103, 246, 211, 83, 125, 196, 247, 78, 106, 148, 9, 211, 245, 132, 59, 105, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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