← previous blocknext block →recent activity
Analyzing
Block #87,624,018
24 transactions · 21 stateful · 2026-07-14 04:01:05 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,624,018 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w18w09w110w216w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd379a368…fea4
0x34b655…2a6f
6 touches
3 conflicts
0x1175233a…64e7
0x34b655…2a6f
6 touches
3 conflicts
0x25329a48…4e00
0x34b655…2a6f
6 touches
3 conflicts
0x8e507257…71c1
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xa0af25f7…9129
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xd379a36873…4efea4
Audit this contract →
← previous block·next block →recent activity