← previous blocknext block →recent activity
Analyzing
Block #87,695,219
21 transactions · 20 stateful · 2026-07-14 11:56:53 UTC
Parallelism
81/100
Blocked
20%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,695,219 · 21 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
2w03w04w17w08w012w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xb8431b57…6825
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xa0acdcf7…bd86
0x34b655…2a6f
6 touches
3 conflicts
0x62222abd…e410
0x34b655…2a6f
6 touches
3 conflicts
0xe4b8f2c5…f54d
0x34b655…2a6f
4 touches
1 conflict
0x4688dd30…ef52
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7212
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity