Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af570f0fb48256d7c43dc12b798ef08e1c02535a4a348ba85c6bc921469384db

Tx prefix hash: c976d5fe77891eefa5f108e883032e3e9fd40f180a129ca0811df2e55738de71
Tx public key: 4cf01a7b20f0466801dc1a38c883c2c54a1bebeb95c3b164c73e5afadfeacd5a
Timestamp: 1732037142 Timestamp [UCT]: 2024-11-19 17:25:42 Age [y:d:h:m:s]: 00:125:06:59:50
Block: 1157262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89345 RingCT/type: yes/0
Extra: 014cf01a7b20f0466801dc1a38c883c2c54a1bebeb95c3b164c73e5afadfeacd5a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83fc2b06f9f85be0e41e98c5f750e4e4491186431fe48ff2f7bacdebe452766d 0.600000000000 1642885 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": 1157272, "vin": [ { "gen": { "height": 1157262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83fc2b06f9f85be0e41e98c5f750e4e4491186431fe48ff2f7bacdebe452766d" } } ], "extra": [ 1, 76, 240, 26, 123, 32, 240, 70, 104, 1, 220, 26, 56, 200, 131, 194, 197, 74, 27, 235, 235, 149, 195, 177, 100, 199, 62, 90, 250, 223, 234, 205, 90, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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