← previous blocknext block →recent activity
Analyzing
Block #87,751,056
19 transactions · 19 stateful · 2026-07-14 18:10:51 UTC
Parallelism
74/100
Blocked
26%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,751,056 · 19 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
1w03w14w25w310w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x366f651e…6100
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xff8fb7ba…30cc
0x34b655…2a6f
6 touches
3 conflicts
0xa1002523…644f
0x34b655…2a6f
6 touches
3 conflicts
0x95cb92ec…1b2b
0x34b655…2a6f
6 touches
3 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
6 touches
3 conflicts
0x6ca32a09…4e48
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
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 0x366f651e17…e36100
Audit this contract →
← previous block·next block →recent activity