Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b93d0b2b9bfea96636571086ca3a4b0951475ad13c38f5085f61ded7c6bef8ef

Tx prefix hash: 0e0845ce63b3b8a3107af9dd759f5948636b30e8b53004d3fb768bb3d47fc9b6
Tx public key: 7afe13ac09be12a19f9a53e592dd5a280a728ceeb925a07c66f70df90a0cca71
Timestamp: 1729947507 Timestamp [UCT]: 2024-10-26 12:58:27 Age [y:d:h:m:s]: 00:235:16:30:32
Block: 1139992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168142 RingCT/type: yes/0
Extra: 017afe13ac09be12a19f9a53e592dd5a280a728ceeb925a07c66f70df90a0cca710211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 163443e6367fce94592330e68abc917e0c201507a8d55a2f6e3b3552940d5b74 0.600000000000 1623783 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": 1140002, "vin": [ { "gen": { "height": 1139992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "163443e6367fce94592330e68abc917e0c201507a8d55a2f6e3b3552940d5b74" } } ], "extra": [ 1, 122, 254, 19, 172, 9, 190, 18, 161, 159, 154, 83, 229, 146, 221, 90, 40, 10, 114, 140, 238, 185, 37, 160, 124, 102, 247, 13, 249, 10, 12, 202, 113, 2, 17, 0, 0, 0, 1, 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