Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4749dd59d70ee4091f947cc4857dc85a6dca68b4dd9b83bb55dc5c9581aba76

Tx prefix hash: 0355d52ec3d75ea70ff23095cffeb29c30901a3230b6bc726134b2e3d24f628e
Tx public key: d0b0872b2c5eb9c7a8a82ed663f77a37c2a40821e9ef4ec521522efdc1551cf8
Timestamp: 1712527220 Timestamp [UCT]: 2024-04-07 22:00:20 Age [y:d:h:m:s]: 00:323:19:45:37
Block: 995571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231520 RingCT/type: yes/0
Extra: 01d0b0872b2c5eb9c7a8a82ed663f77a37c2a40821e9ef4ec521522efdc1551cf802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abbe7f04914c67f2bcf884f851139ac4c67a9877210c99152ecf86d11df2ba70 0.600000000000 1455981 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": 995581, "vin": [ { "gen": { "height": 995571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abbe7f04914c67f2bcf884f851139ac4c67a9877210c99152ecf86d11df2ba70" } } ], "extra": [ 1, 208, 176, 135, 43, 44, 94, 185, 199, 168, 168, 46, 214, 99, 247, 122, 55, 194, 164, 8, 33, 233, 239, 78, 197, 33, 82, 46, 253, 193, 85, 28, 248, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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