← previous blocknext block →recent activity
Analyzing
Block #87,488,678
17 transactions · 16 stateful · 2026-07-13 12:55:06 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1.24
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,488,678 · 17 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
2w03w14w25w37w08w19w210w412w314w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82437f64…3f11
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x38d1e80d…6623
0x34b655…2a6f
6 touches
3 conflicts
0x4ca81ae8…01d4
0x34b655…2a6f
6 touches
3 conflicts
0x57c8db9d…3979
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x366c7d57…0ed1
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 0x82437f64ff…143f11
Audit this contract →
← previous block·next block →recent activity