← previous blocknext block →recent activity
Analyzing
Block #87,623,855
10 transactions · 9 stateful · 2026-07-14 03:59:59 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.8
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,623,855 · 10 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
2w03w15w06w17w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x07f69062…03ec
0x34b655…2a6f
6 touches
3 conflicts
0x0804b2ba…8a77
0x34b655…2a6f
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
4 touches
1 conflict
0x18e900fa…07f4
0x34b655…2a6f
4 touches
1 conflict
0x1d1917da…01b6
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity