← previous blocknext block →recent activity
Analyzing
Block #90,786,997
25 transactions · 22 stateful · 2026-07-27 13:45:20 UTC
Parallelism
76/100
Blocked
55%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,786,997 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w19w210w311w313w214w116w417w422w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x281e160c…fdf2
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xe6fd79d8…6136
0x34b655…2a6f
6 touches
3 conflicts
0x5e8223c2…c242
0x34b655…2a6f
4 touches
1 conflict
0x66067e58…fbec
0x34b655…2a6f
4 touches
1 conflict
0x780e7804…2463
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
6 conflicts on slot 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity