← previous blocknext block →recent activity
Analyzing
Block #87,902,512
16 transactions · 15 stateful · 2026-07-15 11:03:55 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,902,512 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xcc6e2e88…6569
0x34b655…2a6f
4 touches
1 conflict
0xd78905c8…07a6
0x34b655…2a6f
4 touches
1 conflict
0x9f83113a…dcd8
0x34b655…2a6f
4 touches
1 conflict
0x2fe97017…7451
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xbfc73ccb…386d
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
3 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity