← previous blocknext block →recent activity
Analyzing
Block #90,976,293
19 transactions · 19 stateful · 2026-07-28 05:37:45 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,976,293 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w19w210w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x705ab4ae…0162
0x34b655…2a6f
12 touches
15 conflicts
0x1c0be074…2a3b
0x34b655…2a6f
6 touches
3 conflicts
0x74ba5890…79bc
0x34b655…2a6f
6 touches
3 conflicts
0x922e7a8d…7cff
0x34b655…2a6f
5 touches
3 conflicts
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
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
21 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity