← previous blocknext block →recent activity
Analyzing
Block #87,575,920
14 transactions · 13 stateful · 2026-07-13 22:39:26 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,575,920 · 14 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
6w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68d9d4e4…91b6
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x24e3bf88…17bf
0x34b655…2a6f
6 touches
3 conflicts
0x702cd11f…652b
0x34b655…2a6f
6 touches
3 conflicts
0xbe2f3517…dfb1
0x34b655…2a6f
4 touches
1 conflict
0x32646adf…e05d
0x34b655…2a6f
4 touches
1 conflict
0x3279756c…c1a0
0x34b655…2a6f
4 touches
1 conflict
0x486aed2f…813b
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 0x68d9d4e48b…0391b6
Audit this contract →
← previous block·next block →recent activity