← previous blocknext block →recent activity
Analyzing
Block #83,454,379
11 transactions · 9 stateful · 2026-06-24 20:14:33 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,454,379 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93641233…06f5
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x26731ffc…6b25
0x34b655…2a6f
4 touches
1 conflict
0x28287367…f0f5
0x34b655…2a6f
2 touches
0 conflicts
0x2df5bd93…9e2d
0x34b655…2a6f
2 touches
0 conflicts
0x3550e60a…fe48
0x34b655…2a6f
2 touches
0 conflicts
0x5e4bbd13…1ebb
0x34b655…2a6f
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 0x9364123348…4106f5
Audit this contract →
← previous block·next block →recent activity