← previous blocknext block →recent activity
Analyzing
Block #90,805,248
24 transactions · 21 stateful · 2026-07-27 15:17:11 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,805,248 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w07w18w216w117w018w221w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05e1eba1…6491
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8743e1ba…8331
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
6 touches
3 conflicts
0x513ff642…18e3
0x34b655…2a6f
4 touches
1 conflict
0x58f0f706…46a5
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x05e1eba1fd…456491
Audit this contract →
← previous block·next block →recent activity