← previous blocknext block →recent activity
Analyzing
Block #90,958,286
16 transactions · 16 stateful · 2026-07-28 04:07:09 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
1.75
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,958,286 · 16 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
3w05w16w27w38w411w512w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x155e52ca…fac7
0x34b655…2a6f
10 touches
10 conflicts
0x31d88d27…7617
0x34b655…2a6f
10 touches
10 conflicts
0xb2fa1675…4e07
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x2858a318…0e14
0x34b655…2a6f
8 touches
6 conflicts
0x15da697f…5e6e
0x34b655…2a6f
7 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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity