Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6e694eebeaf59da563bf024e572bca5b41111be0d37cfc58e702a564807ffc1

Tx prefix hash: 73921f727427b207809f688f9375778361dc64bf3b4b9a564cbd13d4de6c3d20
Tx public key: 26cad9e64887d6bab3876fce1bb1b3b38f50f74d105e5103c6efcf0b05c62505
Timestamp: 1718128756 Timestamp [UCT]: 2024-06-11 17:59:16 Age [y:d:h:m:s]: 00:301:22:41:29
Block: 1042048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215776 RingCT/type: yes/0
Extra: 0126cad9e64887d6bab3876fce1bb1b3b38f50f74d105e5103c6efcf0b05c625050211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8895287db2c095c159cc0ec2fdf9f8eea2ea0a22d24ab9110399d3155fb6a580 0.600000000000 1510871 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": 1042058, "vin": [ { "gen": { "height": 1042048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8895287db2c095c159cc0ec2fdf9f8eea2ea0a22d24ab9110399d3155fb6a580" } } ], "extra": [ 1, 38, 202, 217, 230, 72, 135, 214, 186, 179, 135, 111, 206, 27, 177, 179, 179, 143, 80, 247, 77, 16, 94, 81, 3, 198, 239, 207, 11, 5, 198, 37, 5, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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