← previous blocknext block →recent activity
Analyzing
Block #89,543,849
44 transactions · 37 stateful · 2026-07-23 02:01:05 UTC
Parallelism
59/100
Blocked
62%
Avg conflicts / tx
2.18
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #89,543,849 · 44 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w19w010w112w013w114w215w316w417w519w622w723w224w837w1338w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x5c16527f…628c
0x34b655…2a6f
8 touches
6 conflicts
0x69d0a300…67ef
0x34b655…2a6f
8 touches
6 conflicts
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity