← previous blocknext block →recent activity
Analyzing
Block #86,982,864
16 transactions · 14 stateful · 2026-07-11 04:33:07 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,982,864 · 16 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
4w05w18w09w011w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x027ebf1c…3880
0x34b655…2a6f
4 touches
1 conflict
0x155dff63…2af8
0x34b655…2a6f
4 touches
1 conflict
0x1ef60f48…6237
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f0b3141…2117
0x34b655…2a6f
4 touches
1 conflict
0x53c922c1…1f78
0x34b655…2a6f
4 touches
1 conflict
0x5fee1ba0…2520
0x34b655…2a6f
4 touches
1 conflict
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 0x027ebf1c00…f53880
Audit this contract →
← previous block·next block →recent activity