← previous blocknext block →recent activity
Analyzing
Block #87,421,343
19 transactions · 16 stateful · 2026-07-13 05:24:56 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,421,343 · 19 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
4w05w16w27w310w011w112w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x9365e097…ff56
0x34b655…2a6f
8 touches
6 conflicts
0xfb4cb196…8c4a
0x34b655…2a6f
8 touches
6 conflicts
0x30153288…6d46
0x34b655…2a6f
6 touches
3 conflicts
0x458c8f89…d23c
0x34b655…2a6f
6 touches
3 conflicts
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 conflicts
0x8d80cfe4…359f
0x34b655…2a6f
6 touches
3 conflicts
0x3230277c…ef39
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity