← previous blocknext block →recent activity
Analyzing
Block #90,235,183
12 transactions · 11 stateful · 2026-07-25 15:14:31 UTC
Parallelism
58/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,235,183 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x410c23da…5793
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfb67be15…a190
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0xa558e115…fc88
0x34b655…2a6f
4 touches
1 conflict
0xb8746edd…bc38
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
3 conflicts on slot 0x410c23dad5…765793
Audit this contract →
← previous block·next block →recent activity