← previous blocknext block →recent activity
Analyzing
Block #87,342,247
11 transactions · 9 stateful · 2026-07-12 20:35:54 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,342,247 · 11 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
5w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xdf15e2bf…d7a9
0x34b655…2a6f
4 touches
1 conflict
0xdfd64ea5…015c
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x149ea1fb…e34a
0x34b655…2a6f
2 touches
0 conflicts
0x4aa300fb…db36
0x34b655…2a6f
2 touches
0 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
2 touches
0 conflicts
0x6e3df932…0d53
0x34b655…2a6f
2 touches
0 conflicts
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity