← previous blocknext block →recent activity
Analyzing
Block #87,902,867
17 transactions · 14 stateful · 2026-07-15 11:06:17 UTC
Parallelism
65/100
Blocked
57%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,902,867 · 17 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
3w05w17w29w310w411w514w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x9f83113a…dcd8
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xb3ae4660…5f75
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe40c96f3…9ce4
0x34b655…2a6f
6 touches
3 conflicts
0x5a36d0c8…12e3
0x34b655…2a6f
6 touches
3 conflicts
0x5a36d0c8…12e2
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity