← previous blocknext block →recent activity
Analyzing
Block #87,878,515
23 transactions · 12 stateful · 2026-07-15 08:23:22 UTC
Parallelism
70/100
Blocked
58%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,878,515 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w28w59w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x147259c6…1709
0x34b655…2a6f
6 touches
3 conflicts
0x2d7b3d63…c856
0x34b655…2a6f
6 touches
3 conflicts
0x367b69ad…33d8
0x34b655…2a6f
6 touches
3 conflicts
0x62dd2f82…fa0c
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity