← previous blocknext block →recent activity
Analyzing
Block #91,543,006
40 transactions · 39 stateful · 2026-07-30 05:12:01 UTC
Parallelism
57/100
Blocked
69%
Avg conflicts / tx
2.77
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #91,543,006 · 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
1w02w14w05w18w09w110w211w012w113w214w315w416w518w621w225w727w828w929w1033w1434w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
12 touches
15 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
10 touches
10 conflicts
0x03aa8b26…118a
0x34b655…2a6f
10 touches
10 conflicts
0x7e1faa73…bfbf
0x34b655…2a6f
10 touches
10 conflicts
0xfbe6a366…8ca1
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity