← previous blocknext block →recent activity
Analyzing
Block #90,800,051
24 transactions · 20 stateful · 2026-07-27 14:51:03 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,800,051 · 24 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
1w02w18w09w111w012w013w215w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa3f6f7c8…2436
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x185ad6db…d46a
0x34b655…2a6f
4 touches
1 conflict
0x1aa62c36…420a
0x34b655…2a6f
4 touches
1 conflict
0x1aa99bc5…cb98
0x34b655…2a6f
4 touches
1 conflict
0x23e3c7fa…5f09
0x34b655…2a6f
4 touches
1 conflict
0x256a5318…6475
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity