← previous blocknext block →recent activity
Analyzing
Block #90,537,633
20 transactions · 16 stateful · 2026-07-26 16:50:53 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,537,633 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w18w29w310w411w413w517w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02c03ee2…3de5
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7a2c83a3…a29a
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x8391fb68…4c83
0x34b655…2a6f
4 touches
1 conflict
0x9c44ab3c…56b3
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
10 conflicts on slot 0x02c03ee228…b43de5
Audit this contract →
← previous block·next block →recent activity