← previous blocknext block →recent activity
Analyzing
Block #90,028,845
34 transactions · 33 stateful · 2026-07-24 21:51:35 UTC
Parallelism
50/100
Blocked
61%
Avg conflicts / tx
4.29
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #90,028,845 · 34 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w29w010w111w212w313w414w515w616w717w818w919w1020w1121w1222w1323w1424w1526w1632w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
34 touches
136 conflicts
0x55b4e430…44cb
0x754704…b603
34 touches
136 conflicts
0x1bff683e…7ecb
0x754704…b603
32 touches
120 conflicts
0x00000000…0005
0x370e2e…63b4
32 touches
120 conflicts
0x4387a428…4385
0x0a2fbf…29b1
18 touches
36 conflicts
0x4387a428…4386
0x0a2fbf…29b1
18 touches
36 conflicts
0x4387a428…4389
0x0a2fbf…29b1
18 touches
36 conflicts
0x2e164e7d…faa8
0x0a2fbf…29b1
16 touches
28 conflicts
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: 0x0a2fbf2d…f729b1
136 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity