Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b106c8ccfe386d7c5615b3cece66aef9d0e177dade9538c31b36a9ab6b7c1366

Tx prefix hash: 5e96b1e6f270bb323c8cb10b367d3632af4b54bad08ba8b8a430a18e891e908e
Tx public key: f85ddae56f603211d1acc7c29d53d3c2784402f516d4c40c149fdccc946c7fba
Timestamp: 1764991467 Timestamp [UCT]: 2025-12-06 03:24:27 Age [y:d:h:m:s]: 00:056:14:26:54
Block: 1427420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40350 RingCT/type: yes/0
Extra: 01f85ddae56f603211d1acc7c29d53d3c2784402f516d4c40c149fdccc946c7fba02110000000dd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 421af9ea5422e2ac51bf21f673a3de56ac74c83d3c1dea1a32ed1ea2b28dfdcb 0.600000000000 1916121 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": 1427430, "vin": [ { "gen": { "height": 1427420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "421af9ea5422e2ac51bf21f673a3de56ac74c83d3c1dea1a32ed1ea2b28dfdcb" } } ], "extra": [ 1, 248, 93, 218, 229, 111, 96, 50, 17, 209, 172, 199, 194, 157, 83, 211, 194, 120, 68, 2, 245, 22, 212, 196, 12, 20, 159, 220, 204, 148, 108, 127, 186, 2, 17, 0, 0, 0, 13, 214, 225, 157, 124, 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