← previous blocknext block →recent activity
Analyzing
Block #84,526,866
11 transactions · 11 stateful · 2026-06-29 19:24:52 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,526,866 · 11 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
4w05w16w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c6d3d6d…9deb
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x02b09e7d…3bc9
0x34b655…2a6f
2 touches
0 conflicts
0x06a2bc66…9610
0x34b655…2a6f
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x0a8f8b9c…3046
0x34b655…2a6f
2 touches
0 conflicts
0x43d16f2c…afaf
0x34b655…2a6f
2 touches
0 conflicts
0x5e87912c…7836
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 0x7c6d3d6daa…059deb
Audit this contract →
← previous block·next block →recent activity