← previous blocknext block →recent activity
Analyzing
Block #90,523,656
15 transactions · 14 stateful · 2026-07-26 15:40:35 UTC
Parallelism
60/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,523,656 · 15 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
2w03w04w15w26w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb8dadd6…5560
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0xb7fb66e8…4f94
0x34b655…2a6f
6 touches
3 conflicts
0xe9991812…e391
0x34b655…2a6f
4 touches
1 conflict
0xe9ba215a…1076
0x34b655…2a6f
4 touches
1 conflict
0xef1de905…0582
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
6 conflicts on slot 0xfb8dadd648…285560
Audit this contract →
← previous block·next block →recent activity