← previous blocknext block →recent activity
Analyzing
Block #90,698,369
9 transactions · 9 stateful · 2026-07-27 06:19:30 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,698,369 · 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
2w03w14w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfab3c44c…2653
0x34b655…2a6f
6 touches
3 conflicts
0x3a0bcd1f…2436
0x34b655…2a6f
4 touches
1 conflict
0x45edc4d2…691f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d914960…a452
0x34b655…2a6f
4 touches
1 conflict
0x6483a537…b63e
0x34b655…2a6f
4 touches
1 conflict
0x6483a537…b63f
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
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 0xfab3c44ca8…bf2653
Audit this contract →
← previous block·next block →recent activity