Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab9391194a22f4bd77b2937d7ddd7d3c0f595d25a8adc10013360116693fe6a6

Tx prefix hash: fa718a42e981d9583114f8f27f716454c1694a81cca7a22f1fb548a6eaece947
Tx public key: 0e1ea5ba2ab0bf20a55af0445f2e69b15ecf8950e54b5b48c3a0813040948897
Timestamp: 1713801050 Timestamp [UCT]: 2024-04-22 15:50:50 Age [y:d:h:m:s]: 00:307:18:23:29
Block: 1006167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219985 RingCT/type: yes/0
Extra: 010e1ea5ba2ab0bf20a55af0445f2e69b15ecf8950e54b5b48c3a081304094889702110000001052d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df64ff432d8f7ab55eb0c817a6675b15c8dbb3297ec19d6cc8aeb6aa33ee4e32 0.600000000000 1467101 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": 1006177, "vin": [ { "gen": { "height": 1006167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df64ff432d8f7ab55eb0c817a6675b15c8dbb3297ec19d6cc8aeb6aa33ee4e32" } } ], "extra": [ 1, 14, 30, 165, 186, 42, 176, 191, 32, 165, 90, 240, 68, 95, 46, 105, 177, 94, 207, 137, 80, 229, 75, 91, 72, 195, 160, 129, 48, 64, 148, 136, 151, 2, 17, 0, 0, 0, 16, 82, 212, 126, 148, 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