← previous blocknext block →recent activity
Analyzing
Block #90,689,043
11 transactions · 11 stateful · 2026-07-27 05:32:35 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,689,043 · 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
4w05w16w07w28w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xe8497ba6…da0e
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x6047f014…4702
0x40c49f…2af0
4 touches
1 conflict
0x62dbeb4d…a388
0x34b655…2a6f
4 touches
1 conflict
0x72bed6a9…14ab
0x34b655…2a6f
4 touches
1 conflict
0x77d7569b…8ccc
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 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity