← previous blocknext block →recent activity
Analyzing
Block #87,311,217
18 transactions · 18 stateful · 2026-07-12 17:08:24 UTC
Parallelism
72/100
Blocked
22%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,311,217 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w09w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xcffc8fcf…ff81
0x34b655…2a6f
6 touches
3 conflicts
0x363a4317…87d2
0x34b655…2a6f
6 touches
3 conflicts
0x79d50d4a…951d
0x34b655…2a6f
6 touches
3 conflicts
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x2c726bac…d4ed
0x34b655…2a6f
4 touches
1 conflict
0xc0877646…595a
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity