← previous blocknext block →recent activity
Analyzing
Block #90,894,730
19 transactions · 19 stateful · 2026-07-27 22:47:27 UTC
Parallelism
74/100
Blocked
58%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,894,730 · 19 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
1w02w16w07w08w19w210w111w312w213w414w215w317w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8252706a…7ca5
0x34b655…2a6f
8 touches
6 conflicts
0x89678d1b…463e
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xa1ff0729…0146
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x52b477bc…7ccf
0x34b655…2a6f
4 touches
1 conflict
0x61681cb3…aa6d
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 0x8252706a8a…797ca5
Audit this contract →
← previous block·next block →recent activity