← previous blocknext block →recent activity
Analyzing
Block #89,687,968
23 transactions · 20 stateful · 2026-07-23 17:13:36 UTC
Parallelism
52/100
Blocked
65%
Avg conflicts / tx
1.87
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #89,687,968 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w511w612w713w814w117w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x7a2c83a3…a29a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb5a47a02…d364
0x34b655…2a6f
6 touches
3 conflicts
0x434010de…83fe
0x34b655…2a6f
6 touches
3 conflicts
0xe9991812…e391
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xac28c0f0…79c2
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity