Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba2e98776c0dea8b2be387a94e9e7195ecf9f657ba9bcca4b86baf968be24d90

Tx prefix hash: 5d9c9d15c5618b536c7b97d8b8100a1496b88a35daf815a429aaafed285e8a4e
Tx public key: 0db5c2060b2bdbe7373be0bf64a2458ee85d6bc1d8d8950bf9054794717445d6
Timestamp: 1725034895 Timestamp [UCT]: 2024-08-30 16:21:35 Age [y:d:h:m:s]: 00:221:04:39:21
Block: 1099284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157950 RingCT/type: yes/0
Extra: 010db5c2060b2bdbe7373be0bf64a2458ee85d6bc1d8d8950bf9054794717445d6021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e6c5085e6c7e2ca3398f322f52c0bd357cc822aebd2d2bb7943061ec5985019 0.600000000000 1575241 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": 1099294, "vin": [ { "gen": { "height": 1099284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e6c5085e6c7e2ca3398f322f52c0bd357cc822aebd2d2bb7943061ec5985019" } } ], "extra": [ 1, 13, 181, 194, 6, 11, 43, 219, 231, 55, 59, 224, 191, 100, 162, 69, 142, 232, 93, 107, 193, 216, 216, 149, 11, 249, 5, 71, 148, 113, 116, 69, 214, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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