← previous blocknext block →recent activity
Analyzing
Block #91,098,852
31 transactions · 29 stateful · 2026-07-28 15:55:15 UTC
Parallelism
48/100
Blocked
66%
Avg conflicts / tx
4.16
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #91,098,852 · 31 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w08w19w210w311w412w513w614w715w816w917w1018w1119w1220w1321w1422w1526w127w229w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
32 touches
120 conflicts
0x705ab4ae…0162
0x34b655…2a6f
24 touches
66 conflicts
0xbde524f4…43bf
0x34b655…2a6f
24 touches
66 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
22 touches
55 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xfdcedc5c…7746
0x34b655…2a6f
10 touches
10 conflicts
0xbf7bff89…1c5a
0x34b655…2a6f
9 touches
10 conflicts
0xc824469a…6426
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
120 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity