← previous blocknext block →recent activity
Analyzing
Block #89,560,027
16 transactions · 15 stateful · 2026-07-23 03:49:07 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,560,027 · 16 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
1w02w13w24w05w16w17w210w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xff9eec93…1598
0x08dd3d…a583
6 touches
3 conflicts
0x00000000…0003
0x0a4fcb…a602
6 touches
3 conflicts
0x2b936aa5…05e2
0x141b1d…9583
6 touches
3 conflicts
0x2b936aa5…05e3
0x141b1d…9583
6 touches
3 conflicts
0x2b936aa5…05e5
0x141b1d…9583
6 touches
3 conflicts
0x02d895f0…2b93
0x34b655…2a6f
6 touches
3 conflicts
0xab39f3a1…b682
0x754704…b603
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity