← previous blocknext block →recent activity
Analyzing
Block #90,291,768
9 transactions · 9 stateful · 2026-07-25 20:00:27 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,291,768 · 9 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
4w05w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d5a6f66…aba7
0x34b655…2a6f
6 touches
3 conflicts
0x0649b8e0…c704
0x34b655…2a6f
4 touches
1 conflict
0x0c119c6d…a42e
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x11431f9d…42c5
0x34b655…2a6f
4 touches
1 conflict
0x120847e2…98c2
0x34b655…2a6f
4 touches
1 conflict
0x150bc0af…34d8
0x34b655…2a6f
4 touches
1 conflict
0x47573147…4356
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 0x7d5a6f66a7…5eaba7
Audit this contract →
← previous block·next block →recent activity