← previous blocknext block →recent activity
Analyzing
Block #90,036,232
17 transactions · 17 stateful · 2026-07-24 22:28:46 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,036,232 · 17 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
2w05w06w08w19w212w315w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf1faa605…f919
0x34b655…2a6f
8 touches
6 conflicts
0xca011cc9…731f
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0xa6848351…2238
0x34b655…2a6f
5 touches
3 conflicts
0x3dc8ed8f…9df1
0x34b655…2a6f
4 touches
1 conflict
0x4362fbd2…e285
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 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity