Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9177bdcfd2591c3b715075d12ff2ac15d3cccba2c33ad8bb2dda4db651a9e07d

Tx prefix hash: 49175d0db3bf3ad287948d6efaedcb02339312c86707a662c2ab0a2485c6928e
Tx public key: 89472c1a10d6adb9e163adcc77ccfe3ca010475352a0e5a1f7fb3079d932fb57
Timestamp: 1719267639 Timestamp [UCT]: 2024-06-24 22:20:39 Age [y:d:h:m:s]: 00:310:04:10:55
Block: 1051469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221660 RingCT/type: yes/0
Extra: 0189472c1a10d6adb9e163adcc77ccfe3ca010475352a0e5a1f7fb3079d932fb570211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ad8003c77442dc32f6f51b4580cf44b27f8118513fb33c7bd6fb826524b376f 0.600000000000 1521782 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": 1051479, "vin": [ { "gen": { "height": 1051469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ad8003c77442dc32f6f51b4580cf44b27f8118513fb33c7bd6fb826524b376f" } } ], "extra": [ 1, 137, 71, 44, 26, 16, 214, 173, 185, 225, 99, 173, 204, 119, 204, 254, 60, 160, 16, 71, 83, 82, 160, 229, 161, 247, 251, 48, 121, 217, 50, 251, 87, 2, 17, 0, 0, 0, 3, 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