← previous blocknext block →recent activity
Analyzing
Block #91,763,712
42 transactions · 41 stateful · 2026-07-30 23:42:14 UTC
Parallelism
69/100
Blocked
61%
Avg conflicts / tx
2.17
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #91,763,712 · 42 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w07w08w110w011w112w213w314w415w516w617w719w120w426w127w528w229w630w831w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8252706a…7ca5
0x34b655…2a6f
8 touches
6 conflicts
0x49bc9efc…8842
0x34b655…2a6f
8 touches
6 conflicts
0x4c4966df…a6db
0xd32edf…ff58
7 touches
6 conflicts
0x01e39429…f244
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity