← previous blocknext block →recent activity
Analyzing
Block #87,596,632
23 transactions · 18 stateful · 2026-07-14 00:57:59 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,596,632 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w011w114w215w116w317w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2be09ff3…ce49
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x158becdc…73ed
0x34b655…2a6f
4 touches
1 conflict
0x1e6234e2…4590
0x34b655…2a6f
4 touches
1 conflict
0x44b80fe8…bfa7
0x34b655…2a6f
4 touches
1 conflict
0x4cf39eee…2213
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
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 0x2be09ff364…0bce49
Audit this contract →
← previous block·next block →recent activity