← previous blocknext block →recent activity
Analyzing
Block #87,610,371
23 transactions · 18 stateful · 2026-07-14 02:29:51 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,610,371 · 23 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
3w07w08w19w111w214w315w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3560a56c…d95d
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x27b9caf2…c102
0x34b655…2a6f
4 touches
1 conflict
0x2bfb71b5…3a04
0x34b655…2a6f
4 touches
1 conflict
0x2bfb71b5…3a05
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x68bec689…fccd
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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 0x3560a56c3c…9cd95d
Audit this contract →
← previous block·next block →recent activity