← previous blocknext block →recent activity
Analyzing
Block #91,210,676
53 transactions · 47 stateful · 2026-07-29 01:17:46 UTC
Parallelism
66/100
Blocked
66%
Avg conflicts / tx
2.45
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #91,210,676 · 53 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w19w010w111w214w015w116w017w122w226w527w628w729w233w335w836w937w1038w1141w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xbc66586e…20fe
0x34b655…2a6f
12 touches
15 conflicts
0xefcdf197…96a2
0x34b655…2a6f
8 touches
6 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
8 touches
6 conflicts
0xb56f0740…7542
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity