← previous blocknext block →recent activity
Analyzing
Block #91,296,118
40 transactions · 37 stateful · 2026-07-29 08:28:29 UTC
Parallelism
57/100
Blocked
76%
Avg conflicts / tx
3.05
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #91,296,118 · 40 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w07w18w29w310w411w012w113w214w315w419w420w521w122w223w326w628w832w1137w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xfd42a6b9…4c81
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x3d158563…8713
0x34b655…2a6f
8 touches
6 conflicts
0x34a1ee7e…fb20
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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity