← previous blocknext block →recent activity
Analyzing
Block #87,341,567
11 transactions · 11 stateful · 2026-07-12 20:31:22 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,341,567 · 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
2w03w04w15w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3ce81c6…d48d
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x44e1c038…95f7
0x34b655…2a6f
4 touches
1 conflict
0x44e1c038…95f8
0x34b655…2a6f
4 touches
1 conflict
0x71a5a556…ba56
0x34b655…2a6f
4 touches
1 conflict
0x7267f4a8…9eb7
0x34b655…2a6f
4 touches
1 conflict
0x7b0283cc…c225
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 0xe3ce81c686…e3d48d
Audit this contract →
← previous block·next block →recent activity