← previous blocknext block →recent activity
Analyzing
Block #86,786,053
18 transactions · 12 stateful · 2026-07-10 06:37:31 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.22
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,786,053 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w012w113w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x119694b6…b8dc
0x34b655…2a6f
4 touches
1 conflict
0xfc90a38d…93f5
0x34b655…2a6f
4 touches
1 conflict
0xc3688185…9b36
0x34b655…2a6f
4 touches
1 conflict
0xbb277c58…e388
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7d07e5f7…6703
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x119694b61e…e0b8dc
Audit this contract →
← previous block·next block →recent activity