← previous blocknext block →recent activity
Analyzing
Block #83,454,837
15 transactions · 13 stateful · 2026-06-24 20:17:37 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,454,837 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w010w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x680fdd59…e84d
0x34b655…2a6f
4 touches
1 conflict
0xee7978e9…2869
0x34b655…2a6f
4 touches
1 conflict
0xf7468e81…86e5
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x7a12283f…b18a
0x69df8a…6292
2 touches
0 conflicts
0x915c095e…c1e5
0x69df8a…6292
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity