← previous blocknext block →recent activity
Analyzing
Block #90,026,745
18 transactions · 12 stateful · 2026-07-24 21:40:59 UTC
Parallelism
72/100
Blocked
58%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,026,745 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w110w211w312w214w117w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22ce1aa0…6e58
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xfbc2809e…bb6d
0x34b655…2a6f
6 touches
3 conflicts
0x3727225e…a3cf
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x22ce1aa032…176e58
Audit this contract →
← previous block·next block →recent activity