Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ab2e7f3eabd27103ef4567606241892fdb92e9213ef66585a24377733a965a6

Tx prefix hash: ff620b7d56a5fe3f0dd52b8b51b88c8d3e371894e8218a46175ae3f1d3ba29c9
Tx public key: 978654a2b0e8247a5007d7ceb20ae47aef123819992b5fd7e691da69304daace
Timestamp: 1638771686 Timestamp [UCT]: 2021-12-06 06:21:26 Age [y:d:h:m:s]: 03:331:18:07:45
Block: 389469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1013526 RingCT/type: yes/0
Extra: 01978654a2b0e8247a5007d7ceb20ae47aef123819992b5fd7e691da69304daace021100000001e9564d6f000000000000000000

1 output(s) for total of 31.443283656000 dcy

stealth address amount amount idx
00: 2f1df46c610e7ecce906a5b4a9a5fcca3f5e3e616b60d784ac24fbd0b463d1a3 31.443283656000 784638 of 0

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": 389479, "vin": [ { "gen": { "height": 389469 } } ], "vout": [ { "amount": 31443283656, "target": { "key": "2f1df46c610e7ecce906a5b4a9a5fcca3f5e3e616b60d784ac24fbd0b463d1a3" } } ], "extra": [ 1, 151, 134, 84, 162, 176, 232, 36, 122, 80, 7, 215, 206, 178, 10, 228, 122, 239, 18, 56, 25, 153, 43, 95, 215, 230, 145, 218, 105, 48, 77, 170, 206, 2, 17, 0, 0, 0, 1, 233, 86, 77, 111, 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