← previous blocknext block →recent activity
Analyzing
Block #90,535,905
8 transactions · 8 stateful · 2026-07-26 16:42:12 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,535,905 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x9af5f9b9…06e8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcc69885f…792f
0x1c3332…a5f4
2 touches
0 conflicts
0xcc69885f…7931
0x1c3332…a5f4
2 touches
0 conflicts
0xcc69885f…7932
0x1c3332…a5f4
2 touches
0 conflicts
0x8698cd50…9200
0x1c8a33…d316
2 touches
0 conflicts
0xcf0ea77e…73db
0x1c8a33…d316
2 touches
0 conflicts
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity