← previous blocknext block →recent activity
Analyzing
Block #87,579,620
18 transactions · 17 stateful · 2026-07-13 23:04:11 UTC
Parallelism
67/100
Blocked
35%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,579,620 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w07w18w09w210w012w114w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5420e1f…3788
0x34b655…2a6f
6 touches
3 conflicts
0xad5139c1…38c6
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x2d651956…12e8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x6638e124…bc7f
0x34b655…2a6f
4 touches
1 conflict
0x71cd2af8…dbd4
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xa5420e1f33…6e3788
Audit this contract →
← previous block·next block →recent activity