← previous blocknext block →recent activity
Analyzing
Block #87,580,957
13 transactions · 12 stateful · 2026-07-13 23:13:08 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,580,957 · 13 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
6w07w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5420e1f…3788
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x311d243d…3396
0x34b655…2a6f
4 touches
1 conflict
0x311d243d…3397
0x34b655…2a6f
4 touches
1 conflict
0x3312fcbd…c934
0x34b655…2a6f
4 touches
1 conflict
0x5250e2f6…9390
0x34b655…2a6f
4 touches
1 conflict
0x6323c5ea…ce8a
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 0xa5420e1f33…6e3788
Audit this contract →
← previous block·next block →recent activity