← previous blocknext block →recent activity
Analyzing
Block #90,448,201
15 transactions · 13 stateful · 2026-07-26 09:20:59 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,448,201 · 15 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
4w05w07w18w29w212w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec501e17…45fd
0x34b655…2a6f
6 touches
3 conflicts
0x34a2c248…f7ed
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf0ba2726…2371
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xc4dc32ca…83fa
0x34b655…2a6f
4 touches
1 conflict
0xd42cf33e…e446
0x34b655…2a6f
4 touches
1 conflict
0xd5ddc44a…3224
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 0xec501e1764…5245fd
Audit this contract →
← previous block·next block →recent activity