← previous blocknext block →recent activity
Analyzing
Block #87,048,307
14 transactions · 13 stateful · 2026-07-11 11:50:27 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,048,307 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xc5decd02…dbf4
0x34b655…2a6f
4 touches
1 conflict
0x6b22f8eb…68cb
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa248a5dd…4a69
0x34b655…2a6f
4 touches
1 conflict
0xa46242d8…c0a8
0x34b655…2a6f
4 touches
1 conflict
0x53e8bd9c…11db
0x40c49f…2af0
2 touches
0 conflicts
0x5ed52385…8f72
0x40c49f…2af0
2 touches
0 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
1 conflict on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity