← previous blocknext block →recent activity
Analyzing
Block #87,620,943
14 transactions · 10 stateful · 2026-07-14 03:40:30 UTC
Parallelism
79/100
Blocked
30%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,620,943 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x944bfd2a…49f7
0x34b655…2a6f
4 touches
1 conflict
0xa0acdcf7…bd86
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xc5f5c630…83e4
0x34b655…2a6f
4 touches
1 conflict
0x1f0acb46…bb29
0x34b655…2a6f
2 touches
0 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
2 touches
0 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity