← previous blocknext block →recent activity
Analyzing
Block #87,503,837
33 transactions · 21 stateful · 2026-07-13 14:36:33 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,503,837 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w116w217w018w322w430w531w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4af56d6…5a50
0x34b655…2a6f
8 touches
6 conflicts
0xe5620d52…7ede
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3a5224d1…ee57
0x34b655…2a6f
4 touches
1 conflict
0x4118bd12…924a
0x34b655…2a6f
4 touches
1 conflict
0x448846ce…af2f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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
6 conflicts on slot 0xe4af56d65a…785a50
Audit this contract →
← previous block·next block →recent activity