← previous blocknext block →recent activity
Analyzing
Block #87,725,243
18 transactions · 14 stateful · 2026-07-14 15:18:08 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,725,243 · 18 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
2w03w15w06w17w28w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x1f2cd70b…94be
0x34b655…2a6f
4 touches
1 conflict
0x1fab1722…aec5
0x34b655…2a6f
4 touches
1 conflict
0x2571f435…11bd
0x34b655…2a6f
4 touches
1 conflict
0x2ce195b7…3748
0x34b655…2a6f
4 touches
1 conflict
0x2e8d4fe6…9af7
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity