← previous blocknext block →recent activity
Analyzing
Block #90,029,246
17 transactions · 16 stateful · 2026-07-24 21:53:36 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,029,246 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w09w110w012w113w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x9fd372a1…a959
0x34b655…2a6f
6 touches
3 conflicts
0x0c465526…8a9f
0x0a2fbf…29b1
4 touches
1 conflict
0x0c465526…8aa2
0x0a2fbf…29b1
4 touches
1 conflict
0xcae9f8fd…fc18
0x0a2fbf…29b1
4 touches
1 conflict
0xcae9f8fd…fc19
0x0a2fbf…29b1
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x2e64e234…5cfa
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity