Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04693cc698c98c60fd5c6ddaba32cc9bd45418a96531fda0d22da72587a4ff87

Tx prefix hash: 0bd44c086a9cb0e4c7810a0cf8dcc1fb7da5f6dade75ef5b34c83cb201424a3b
Tx public key: 1bac892a5fe5c720262384a25484db0a8f618720becbec7cdee01448dcb4a1e1
Timestamp: 1760395495 Timestamp [UCT]: 2025-10-13 22:44:55 Age [y:d:h:m:s]: 00:083:23:21:53
Block: 1389352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60130 RingCT/type: yes/0
Extra: 011bac892a5fe5c720262384a25484db0a8f618720becbec7cdee01448dcb4a1e1021100000005df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 849cdb8acab2c1122d6dab5eb9ffc84c55d1a9fe4b12f32d9bffc5d5a96c4387 0.600000000000 1877581 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": 1389362, "vin": [ { "gen": { "height": 1389352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "849cdb8acab2c1122d6dab5eb9ffc84c55d1a9fe4b12f32d9bffc5d5a96c4387" } } ], "extra": [ 1, 27, 172, 137, 42, 95, 229, 199, 32, 38, 35, 132, 162, 84, 132, 219, 10, 143, 97, 135, 32, 190, 203, 236, 124, 222, 224, 20, 72, 220, 180, 161, 225, 2, 17, 0, 0, 0, 5, 223, 90, 36, 122, 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