← previous blocknext block →recent activity
Analyzing
Block #90,276,723
16 transactions · 14 stateful · 2026-07-25 18:44:01 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,276,723 · 16 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
4w05w16w27w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xdd8aef75…2915
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x8d7e3f62…e2cc
0x34b655…2a6f
4 touches
1 conflict
0x8f888556…f387
0x34b655…2a6f
4 touches
1 conflict
0x9ddc4efa…8e27
0x34b655…2a6f
4 touches
1 conflict
0x9f7ff7d3…4a3b
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity