← previous blocknext block →recent activity
Analyzing
Block #90,330,948
16 transactions · 16 stateful · 2026-07-25 23:19:34 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,330,948 · 16 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
6w07w18w09w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x251cc79b…c5e8
0x370e2e…63b4
10 touches
10 conflicts
0x1bff683e…7ecb
0x754704…b603
10 touches
10 conflicts
0x00000000…0006
0x0a2fbf…29b1
10 touches
10 conflicts
0x39861a66…5e03
0x0a2fbf…29b1
10 touches
10 conflicts
0x39861a66…5e04
0x0a2fbf…29b1
10 touches
10 conflicts
0x39861a66…5e07
0x0a2fbf…29b1
10 touches
10 conflicts
0x00000000…0005
0x370e2e…63b4
10 touches
10 conflicts
0xf27bb96a…c923
0x0a2fbf…29b1
10 touches
10 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: 0x370e2ee6…bd63b4
10 conflicts on slot 0x251cc79b8b…53c5e8
Audit this contract →
← previous block·next block →recent activity