← previous blocknext block →recent activity
Analyzing
Block #89,750,371
11 transactions · 10 stateful · 2026-07-23 22:28:35 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,750,371 · 11 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
2w03w15w06w27w18w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fd0b86c…b37c
0x34b655…2a6f
6 touches
3 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2e0a2649…97e0
0x34b655…2a6f
4 touches
1 conflict
0x38c9f326…e153
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
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 0x6fd0b86c31…77b37c
Audit this contract →
← previous block·next block →recent activity