Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88570e94a2220319cbd7a026057e8b25a9636b4660f7a6a3ae3f1a56b006db1f

Tx prefix hash: ec4c5fbf2ab3e101cbd0dd3247ef45f9d517ca8580ee2e6a381a613bb068f2f1
Tx public key: a53c6cf48207b06c54f3fc77e8ce072c336c6925d28895171eacb027763d6995
Timestamp: 1731456542 Timestamp [UCT]: 2024-11-13 00:09:02 Age [y:d:h:m:s]: 00:011:06:17:13
Block: 1152433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8066 RingCT/type: yes/0
Extra: 01a53c6cf48207b06c54f3fc77e8ce072c336c6925d28895171eacb027763d6995021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5079a32cc035be9e37146ba2e3247605259694fb676d3b4a2137a67ef0174c7 0.600000000000 1638030 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": 1152443, "vin": [ { "gen": { "height": 1152433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5079a32cc035be9e37146ba2e3247605259694fb676d3b4a2137a67ef0174c7" } } ], "extra": [ 1, 165, 60, 108, 244, 130, 7, 176, 108, 84, 243, 252, 119, 232, 206, 7, 44, 51, 108, 105, 37, 210, 136, 149, 23, 30, 172, 176, 39, 118, 61, 105, 149, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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