← previous blocknext block →recent activity
Analyzing
Block #87,695,863
21 transactions · 19 stateful · 2026-07-14 12:01:11 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,695,863 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w07w18w09w210w311w414w015w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fdfa032…139c
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0xf324b405…ca30
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x864353d4…dcb7
0x34b655…2a6f
6 touches
3 conflicts
0xca18c58e…cede
0x34b655…2a6f
6 touches
3 conflicts
0xdbb43016…7cc4
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
6 conflicts on slot 0x2fdfa03271…56139c
Audit this contract →
← previous block·next block →recent activity