← previous blocknext block →recent activity
Analyzing
Block #90,204,913
8 transactions · 7 stateful · 2026-07-25 12:41:57 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,204,913 · 8 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
3w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0xc6f31dd4…707b
0x34b655…2a6f
6 touches
3 conflicts
0x2d3930d3…c9b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbd26d3a7…f31a
0x34b655…2a6f
4 touches
1 conflict
0x159cff26…7665
0x34b655…2a6f
4 touches
1 conflict
0xc601b84f…92e7
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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity