← previous blocknext block →recent activity
Analyzing
Block #87,758,036
12 transactions · 11 stateful · 2026-07-14 18:57:29 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,758,036 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w17w08w29w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x051f42ba…45a8
0x34b655…2a6f
4 touches
1 conflict
0x051f42ba…45a9
0x34b655…2a6f
4 touches
1 conflict
0x10ef891f…d726
0x34b655…2a6f
4 touches
1 conflict
0x2fdfe038…c16c
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3fde350e…8d43
0x34b655…2a6f
4 touches
1 conflict
0x587911c7…9e01
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity