← previous blocknext block →recent activity
Analyzing
Block #90,539,520
13 transactions · 13 stateful · 2026-07-26 17:00:23 UTC
Parallelism
62/100
Blocked
31%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,539,520 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8743e1ba…8331
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc6627c72…1898
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x94e7f277…471b
0x34b655…2a6f
4 touches
1 conflict
0xc7954a60…d294
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 0x8743e1bab8…0a8331
Audit this contract →
← previous block·next block →recent activity