← previous blocknext block →recent activity
Analyzing
Block #91,424,060
47 transactions · 43 stateful · 2026-07-29 19:12:47 UTC
Parallelism
64/100
Blocked
70%
Avg conflicts / tx
2.96
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #91,424,060 · 47 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
1w02w13w04w15w26w38w49w010w111w212w313w414w515w616w617w721w822w923w1028w1137w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
26 touches
78 conflicts
0xfd42a6b9…4c81
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xa4e9800f…4ab1
0x34b655…2a6f
16 touches
28 conflicts
0x54f0697c…d70c
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xebac0f82…a49c
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity