← previous blocknext block →recent activity
Analyzing
Block #90,963,167
24 transactions · 24 stateful · 2026-07-28 04:31:42 UTC
Parallelism
42/100
Blocked
63%
Avg conflicts / tx
3.5
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #90,963,167 · 24 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w08w19w210w311w412w513w614w715w816w917w1018w1119w1220w1323w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
26 touches
78 conflicts
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0x705ab4ae…0162
0x34b655…2a6f
20 touches
45 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
18 touches
36 conflicts
0x35e4d749…3a9d
0x34b655…2a6f
12 touches
15 conflicts
0x5e2fca4c…cf4d
0x34b655…2a6f
9 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
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
78 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity