← previous blocknext block →recent activity
Analyzing
Block #90,294,792
20 transactions · 17 stateful · 2026-07-25 20:15:48 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,294,792 · 20 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
3w04w06w17w28w09w110w211w312w413w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
10 touches
10 conflicts
0x17441589…e100
0x0a2fbf…29b1
10 touches
10 conflicts
0x17441589…e101
0x0a2fbf…29b1
10 touches
10 conflicts
0x2b63fd11…3d0e
0x0a2fbf…29b1
10 touches
10 conflicts
0x2b63fd11…3d0f
0x0a2fbf…29b1
10 touches
10 conflicts
0x2b63fd11…3d12
0x0a2fbf…29b1
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0005
0x370e2e…63b4
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: 0x0a2fbf2d…f729b1
10 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity