← previous blocknext block →recent activity
Analyzing
Block #87,615,444
13 transactions · 11 stateful · 2026-07-14 03:03:46 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,615,444 · 13 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
3w04w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x6dcb5d8d…5f07
0x34b655…2a6f
4 touches
1 conflict
0x4fc141d9…bb36
0x34b655…2a6f
4 touches
1 conflict
0x040cccc8…e752
0x34b655…2a6f
2 touches
0 conflicts
0x229a1b07…9f93
0x34b655…2a6f
2 touches
0 conflicts
0x27da6a95…077b
0x34b655…2a6f
2 touches
0 conflicts
0x46361afb…9d6b
0x34b655…2a6f
2 touches
0 conflicts
0x46ddd829…cbf5
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity