← previous blocknext block →recent activity
Analyzing
Block #87,876,286
25 transactions · 16 stateful · 2026-07-15 08:08:28 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,876,286 · 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
1w02w13w211w012w113w120w121w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xd4c913d7…3438
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity