← previous blocknext block →recent activity
Analyzing
Block #90,918,301
14 transactions · 14 stateful · 2026-07-28 00:46:03 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,918,301 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w28w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb44cedd…c666
0x34b655…2a6f
8 touches
6 conflicts
0x7b481037…3457
0x34b655…2a6f
8 touches
6 conflicts
0xcedd9c7b…916e
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x2a00a910…f960
0x34b655…2a6f
6 touches
3 conflicts
0xc7d08bca…e210
0x34b655…2a6f
6 touches
3 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
6 touches
3 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
6 touches
3 conflicts
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 0xbb44cedda5…77c666
Audit this contract →
← previous block·next block →recent activity