← previous blocknext block →recent activity
Analyzing
Block #89,844,388
21 transactions · 21 stateful · 2026-07-24 06:23:07 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,844,388 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w29w110w312w115w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xf156f318…3437
0x34b655…2a6f
6 touches
3 conflicts
0x0bcbbcad…fc9c
0x34b655…2a6f
6 touches
3 conflicts
0x57be321f…fecc
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x5ee667a1…2a60
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity