← previous blocknext block →recent activity
Analyzing
Block #87,441,215
19 transactions · 18 stateful · 2026-07-13 07:37:44 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,441,215 · 19 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
1w02w14w05w16w07w18w211w112w313w416w017w118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xdb88134d…d6c1
0x34b655…2a6f
6 touches
3 conflicts
0xdb88134d…d6c2
0x34b655…2a6f
6 touches
3 conflicts
0x9b02ba92…7100
0x34b655…2a6f
6 touches
3 conflicts
0xe860e8c0…de9b
0x34b655…2a6f
6 touches
3 conflicts
0x5d1ac445…5233
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity