← previous blocknext block →recent activity
Analyzing
Block #90,115,225
23 transactions · 22 stateful · 2026-07-25 05:09:36 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,115,225 · 23 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
5w06w17w08w19w210w311w412w113w414w217w519w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x0181bb37…6628
0x34b655…2a6f
4 touches
1 conflict
0x0181bb37…6629
0x34b655…2a6f
4 touches
1 conflict
0x08024b2c…d265
0x34b655…2a6f
4 touches
1 conflict
0x092b7171…c16d
0x34b655…2a6f
4 touches
1 conflict
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0x0cc65720…396c
0x34b655…2a6f
4 touches
1 conflict
0x2d651956…12e8
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity