← previous blocknext block →recent activity
Analyzing
Block #90,301,417
11 transactions · 11 stateful · 2026-07-25 20:49:30 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,301,417 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w39w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd6255b52…69e7
0x34b655…2a6f
6 touches
3 conflicts
0xf272b97d…1b7b
0x34b655…2a6f
6 touches
3 conflicts
0x26607bc2…7fd6
0x34b655…2a6f
4 touches
1 conflict
0x38badd90…a68c
0x34b655…2a6f
4 touches
1 conflict
0x4b76146e…0dcb
0x34b655…2a6f
4 touches
1 conflict
0x7a4f47ac…3289
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity