← previous blocknext block →recent activity
Analyzing
Block #87,920,900
23 transactions · 20 stateful · 2026-07-15 13:06:53 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,920,900 · 23 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
1w010w011w112w213w316w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe54b7d5…1bda
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x94710b77…a921
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1ff24133…b82d
0x34b655…2a6f
4 touches
1 conflict
0x440b002f…f302
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7213
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 0xbe54b7d5c9…2a1bda
Audit this contract →
← previous block·next block →recent activity