← previous blocknext block →recent activity
Analyzing
Block #90,226,554
35 transactions · 31 stateful · 2026-07-25 14:30:59 UTC
Parallelism
51/100
Blocked
68%
Avg conflicts / tx
4.17
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #90,226,554 · 35 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
4w05w16w17w28w09w110w211w312w413w514w615w716w818w919w1020w1121w1223w1324w1425w1526w1628w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
34 touches
136 conflicts
0x53a79601…7ad7
0x0a2fbf…29b1
34 touches
136 conflicts
0x53a79601…7ad8
0x0a2fbf…29b1
34 touches
136 conflicts
0x53a79601…7adb
0x0a2fbf…29b1
34 touches
136 conflicts
0x75f24f53…3225
0x0a2fbf…29b1
34 touches
136 conflicts
0x75f24f53…3226
0x0a2fbf…29b1
34 touches
136 conflicts
0x00000000…0005
0x370e2e…63b4
34 touches
136 conflicts
0x1bff683e…7ecb
0x754704…b603
34 touches
136 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