← previous blocknext block →recent activity
Analyzing
Block #87,356,316
17 transactions · 14 stateful · 2026-07-12 22:09:58 UTC
Parallelism
65/100
Blocked
64%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,356,316 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w27w38w19w410w512w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf81d0d0f…cf78
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x3be33cca…0fff
0x34b655…2a6f
4 touches
1 conflict
0x3be33cca…1000
0x34b655…2a6f
4 touches
1 conflict
0x42dd9d36…3fc0
0x34b655…2a6f
4 touches
1 conflict
0x49eb4894…b9d1
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
6 conflicts on slot 0xf81d0d0f79…09cf78
Audit this contract →
← previous block·next block →recent activity