← previous blocknext block →recent activity
Analyzing
Block #83,496,556
17 transactions · 16 stateful · 2026-06-25 00:55:51 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,496,556 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w011w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23a320fb…cbd7
0x34b655…2a6f
4 touches
1 conflict
0x6ac6d1bf…8b19
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x078b6829…2b22
0x065c9d…c394
2 touches
0 conflicts
0x1ee86d3b…48d3
0x065c9d…c394
2 touches
0 conflicts
0x36b6b2a9…a4dc
0x065c9d…c394
2 touches
0 conflicts
0x6addf6f0…2919
0x065c9d…c394
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0x23a320fbfb…26cbd7
Audit this contract →
← previous block·next block →recent activity