Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97736efed8f87f5670a74ffbec6af735d2f0263b14c645cd7c807c5608789200

Tx prefix hash: ba02d1a117b04db05f78df222a7e9c7da5cd579c86c07b400051d07d921ff7ea
Tx public key: da0c227dedd59263c1f84a57b28b0e593dd2f6b9af79ad9a49df85b32e5d0d80
Timestamp: 1726794780 Timestamp [UCT]: 2024-09-20 01:13:00 Age [y:d:h:m:s]: 00:201:10:27:36
Block: 1113883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143800 RingCT/type: yes/0
Extra: 01da0c227dedd59263c1f84a57b28b0e593dd2f6b9af79ad9a49df85b32e5d0d8002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e71abbcb4c69e6b73ebab3795f035f9ee1352aadbf696f69defc35624094074 0.600000000000 1593680 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": 1113893, "vin": [ { "gen": { "height": 1113883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e71abbcb4c69e6b73ebab3795f035f9ee1352aadbf696f69defc35624094074" } } ], "extra": [ 1, 218, 12, 34, 125, 237, 213, 146, 99, 193, 248, 74, 87, 178, 139, 14, 89, 61, 210, 246, 185, 175, 121, 173, 154, 73, 223, 133, 179, 46, 93, 13, 128, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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