← previous blocknext block →recent activity
Analyzing
Block #86,798,942
25 transactions · 20 stateful · 2026-07-10 08:03:36 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,798,942 · 25 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
1w03w16w010w111w112w213w314w419w020w121w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x010d4ce0…8cf0
0x34b655…2a6f
4 touches
1 conflict
0x05435a4a…0c07
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x36f9663c…6c66
0x34b655…2a6f
4 touches
1 conflict
0x3a6290da…e683
0x34b655…2a6f
4 touches
1 conflict
0x40a37011…e593
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity