← previous blocknext block →recent activity
Analyzing
Block #91,431,900
46 transactions · 38 stateful · 2026-07-29 19:53:01 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
2.09
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #91,431,900 · 46 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
1w02w04w05w113w014w115w216w317w418w519w521w125w926w227w328w431w134w1135w1238w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x08636046…e60f
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
10 touches
10 conflicts
0x831dbc32…b84a
0x34b655…2a6f
10 touches
10 conflicts
0xfe498a85…9dc4
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity