← previous blocknext block →recent activity
Analyzing
Block #86,971,201
16 transactions · 14 stateful · 2026-07-11 03:15:14 UTC
Parallelism
56/100
Blocked
64%
Avg conflicts / tx
1.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,971,201 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w48w310w111w412w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xefcaccf2…c083
0x34b655…2a6f
8 touches
6 conflicts
0xf5042875…9a93
0x34b655…2a6f
8 touches
6 conflicts
0xafe3acc8…5c1c
0x34b655…2a6f
6 touches
3 conflicts
0xd1c5aeea…ee0a
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 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity