← previous blocknext block →recent activity
Analyzing
Block #86,386,972
19 transactions · 18 stateful · 2026-07-08 10:08:29 UTC
Parallelism
74/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,386,972 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w08w09w110w111w214w115w017w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95d6e198…f79c
0x34b655…2a6f
6 touches
3 conflicts
0x1c8a3a66…2a9c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x59645a97…3ca1
0x34b655…2a6f
4 touches
1 conflict
0x5ee85555…f443
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x8d773511…5fd3
0x34b655…2a6f
4 touches
1 conflict
0x9ea24fe7…056c
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
3 conflicts on slot 0x95d6e1989e…e0f79c
Audit this contract →
← previous block·next block →recent activity