← previous blocknext block →recent activity
Analyzing
Block #90,719,127
13 transactions · 12 stateful · 2026-07-27 08:03:55 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,719,127 · 13 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
5w06w17w211w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca125b62…fb1c
0x34b655…2a6f
4 touches
1 conflict
0x5a3a03c4…e559
0x34b655…2a6f
4 touches
1 conflict
0x04bacba0…9b54
0x34b655…2a6f
4 touches
1 conflict
0xff9e45bf…99a0
0x34b655…2a6f
4 touches
1 conflict
0x787e6b5e…3130
0x34b655…2a6f
4 touches
1 conflict
0x327c57dd…836d
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity