← previous blocknext block →recent activity
Analyzing
Block #90,960,111
31 transactions · 28 stateful · 2026-07-28 04:16:20 UTC
Parallelism
55/100
Blocked
68%
Avg conflicts / tx
2.39
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #90,960,111 · 31 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w08w19w210w311w412w514w515w616w717w818w219w120w925w1026w1127w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
12 touches
15 conflicts
0x6e6b8ec7…2197
0x34b655…2a6f
10 touches
10 conflicts
0x957c875f…b3f9
0x34b655…2a6f
8 touches
6 conflicts
0x0f3152e8…f181
0x34b655…2a6f
8 touches
6 conflicts
0x51ed538f…f725
0x34b655…2a6f
8 touches
6 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
8 touches
6 conflicts
0xcc58c80b…ff79
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity