← previous blocknext block →recent activity
Analyzing
Block #89,736,408
25 transactions · 23 stateful · 2026-07-23 21:18:00 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
1.16
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #89,736,408 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w07w18w211w012w113w214w316w417w519w120w222w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3383813…4a0c
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x78346476…4311
0x34b655…2a6f
6 touches
3 conflicts
0xa3f095f5…bd87
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
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 0xf338381336…ec4a0c
Audit this contract →
← previous block·next block →recent activity