← previous blocknext block →recent activity
Analyzing
Block #86,855,107
21 transactions · 19 stateful · 2026-07-10 14:19:10 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,855,107 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w29w310w311w412w518w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
10 touches
10 conflicts
0xc92ea287…c4df
0x34b655…2a6f
8 touches
6 conflicts
0xa523c16d…15cd
0x34b655…2a6f
8 touches
6 conflicts
0x94ed0437…073c
0x34b655…2a6f
8 touches
6 conflicts
0x9d64d7f8…ce93
0x34b655…2a6f
6 touches
3 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
6 touches
3 conflicts
0x38489774…2811
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity