Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1ae3e2ad27100ecc3acdaf370f6e19d00d12ccf5c85ce197f4a0389780a411e

Tx prefix hash: 98127c5036bef6f4c3fa72af8f824cc87d380b62037f2d6eda5773ccb822bfe4
Tx public key: 7b51264d96ad664dbb2171db3bc0a0b54a807df479f179e847434de9f27e28fe
Timestamp: 1705002639 Timestamp [UCT]: 2024-01-11 19:50:39 Age [y:d:h:m:s]: 01:093:17:50:41
Block: 933200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328111 RingCT/type: yes/0
Extra: 017b51264d96ad664dbb2171db3bc0a0b54a807df479f179e847434de9f27e28fe0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f523f5aa67f794106141e0b9bb1a5bc859b0e2f2c87999d87d9bb51bf141f226 0.600000000000 1391160 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": 933210, "vin": [ { "gen": { "height": 933200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f523f5aa67f794106141e0b9bb1a5bc859b0e2f2c87999d87d9bb51bf141f226" } } ], "extra": [ 1, 123, 81, 38, 77, 150, 173, 102, 77, 187, 33, 113, 219, 59, 192, 160, 181, 74, 128, 125, 244, 121, 241, 121, 232, 71, 67, 77, 233, 242, 126, 40, 254, 2, 17, 0, 0, 0, 4, 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