← previous blocknext block →recent activity
Analyzing
Block #87,577,642
18 transactions · 14 stateful · 2026-07-13 22:50:57 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,577,642 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w38w49w512w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed4a0d72…065f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x1ee4a6d2…6389
0x34b655…2a6f
4 touches
1 conflict
0x25329a48…4e00
0x34b655…2a6f
4 touches
1 conflict
0x3c8c4674…a567
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4afc8b31…0377
0x34b655…2a6f
4 touches
1 conflict
0x4cf44a87…e320
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 0xed4a0d72e2…41065f
Audit this contract →
← previous block·next block →recent activity