← previous blocknext block →recent activity
Analyzing
Block #87,716,398
25 transactions · 24 stateful · 2026-07-14 14:18:57 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,716,398 · 25 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
1w03w07w08w19w213w114w116w119w222w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b818135…eff8
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7525206c…fbd5
0x34b655…2a6f
6 touches
3 conflicts
0xc0fb0790…a482
0x34b655…2a6f
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x5b145de0…367c
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x8b81813549…3ceff8
Audit this contract →
← previous block·next block →recent activity