← previous blocknext block →recent activity
Analyzing
Block #89,528,341
20 transactions · 18 stateful · 2026-07-23 00:17:31 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,528,341 · 20 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
3w04w15w06w17w210w311w414w518w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4b3f3e9f…1e0d
0x34b655…2a6f
6 touches
3 conflicts
0x3ecef1ff…9295
0x34b655…2a6f
4 touches
1 conflict
0x4415b622…56a9
0x34b655…2a6f
4 touches
1 conflict
0x457e8f5d…1137
0x34b655…2a6f
4 touches
1 conflict
0x4af37265…5aa5
0x34b655…2a6f
4 touches
1 conflict
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0x5d863b2f…bd28
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity