← previous blocknext block →recent activity
Analyzing
Block #87,900,422
23 transactions · 23 stateful · 2026-07-15 10:49:56 UTC
Parallelism
87/100
Blocked
30%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,900,422 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w19w110w011w114w216w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x30f3ece3…c237
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x94bc4ddb…1751
0x0a2fbf…29b1
4 touches
1 conflict
0x94bc4ddb…1752
0x0a2fbf…29b1
4 touches
1 conflict
0x94bc4ddb…1755
0x0a2fbf…29b1
4 touches
1 conflict
0x077d58c3…8ed7
0x34b655…2a6f
4 touches
1 conflict
0x3ca2d168…7611
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity