← previous blocknext block →recent activity
Analyzing
Block #90,328,697
14 transactions · 13 stateful · 2026-07-25 23:08:09 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,328,697 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w27w311w012w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x68bec689…fccd
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3a1edb3e…b841
0x34b655…2a6f
4 touches
1 conflict
0x41bc5f7b…26f2
0x34b655…2a6f
4 touches
1 conflict
0x4d7e366b…7690
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity