Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86e93f988cbb8f2a9fbae022d5da41dbbcc3f1fc3dc17a5253941f5296eb3a6b

Tx prefix hash: 8c59f8ab90581903394faa32dd6c7b9b24a8f9ca8af2a6694c1009390a386df7
Tx public key: e267a6f8bc39724866a0470dc412331a53a6b899876816bb02035878bae6d151
Timestamp: 1738171365 Timestamp [UCT]: 2025-01-29 17:22:45 Age [y:d:h:m:s]: 00:138:22:05:43
Block: 1207794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99246 RingCT/type: yes/0
Extra: 01e267a6f8bc39724866a0470dc412331a53a6b899876816bb02035878bae6d1510211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f4d122e1dc27ddd16e80da08d3ad671a6a8fa16ccdcb9e1f6b3d248813febc6 0.600000000000 1694519 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": 1207804, "vin": [ { "gen": { "height": 1207794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f4d122e1dc27ddd16e80da08d3ad671a6a8fa16ccdcb9e1f6b3d248813febc6" } } ], "extra": [ 1, 226, 103, 166, 248, 188, 57, 114, 72, 102, 160, 71, 13, 196, 18, 51, 26, 83, 166, 184, 153, 135, 104, 22, 187, 2, 3, 88, 120, 186, 230, 209, 81, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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