← previous blocknext block →recent activity
Analyzing
Block #90,066,111
20 transactions · 17 stateful · 2026-07-25 00:59:50 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
0.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,066,111 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w29w313w314w415w516w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xe150cf9f…25d8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0xce75cca8…2fbf
0x34b655…2a6f
6 touches
3 conflicts
0x4e50038e…6e29
0x34b655…2a6f
6 touches
3 conflicts
0x8c5ef7e9…05f7
0x34b655…2a6f
5 touches
3 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: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity