← previous blocknext block →recent activity
Analyzing
Block #90,511,921
12 transactions · 12 stateful · 2026-07-26 14:41:34 UTC
Parallelism
42/100
Blocked
58%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,511,921 · 12 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w611w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bb5c3e4…6da4
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x9fd372a1…a959
0x34b655…2a6f
8 touches
6 conflicts
0xde95b18d…3751
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xabd0bcfc…64e2
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x8bb5c3e478…396da4
Audit this contract →
← previous block·next block →recent activity