← previous blocknext block →recent activity
Analyzing
Block #86,924,591
17 transactions · 16 stateful · 2026-07-10 22:03:47 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.82
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,924,591 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w311w312w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x1535d171…c68b
0x34b655…2a6f
6 touches
3 conflicts
0x17c3727d…cb0e
0x34b655…2a6f
6 touches
3 conflicts
0x3a996b35…bc8f
0x34b655…2a6f
6 touches
3 conflicts
0x6bd6b33e…9557
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
21 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity