Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06ed4e0a528a2d4c785b84af1f49a1a4dd7034b340e5c831b9509713fb9b1505

Tx prefix hash: b224d8116ca292c34689882d28f2008060b5bbe1421b06b30fd9e927449517fb
Tx public key: b26cf17b140f16d01351c874cd17709ac0336cb4f8c96493bd37fd6e3e56f070
Timestamp: 1755347004 Timestamp [UCT]: 2025-08-16 12:23:24 Age [y:d:h:m:s]: 00:097:11:39:38
Block: 1347823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69472 RingCT/type: yes/0
Extra: 01b26cf17b140f16d01351c874cd17709ac0336cb4f8c96493bd37fd6e3e56f07002110000001ab2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0045e87d7944ae1a6ccbc176c496aeb0d8d04bd96edd5a9a1291ae7cee2db8d 0.600000000000 1835744 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": 1347833, "vin": [ { "gen": { "height": 1347823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0045e87d7944ae1a6ccbc176c496aeb0d8d04bd96edd5a9a1291ae7cee2db8d" } } ], "extra": [ 1, 178, 108, 241, 123, 20, 15, 22, 208, 19, 81, 200, 116, 205, 23, 112, 154, 192, 51, 108, 180, 248, 201, 100, 147, 189, 55, 253, 110, 62, 86, 240, 112, 2, 17, 0, 0, 0, 26, 178, 247, 132, 196, 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