← previous blocknext block →recent activity
Analyzing
Block #90,524,042
14 transactions · 13 stateful · 2026-07-26 15:42:32 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,524,042 · 14 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
10w011w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc82f66db…833d
0x34b655…2a6f
4 touches
1 conflict
0xefeb7937…c283
0x34b655…2a6f
4 touches
1 conflict
0xb011544c…9580
0x34b655…2a6f
4 touches
1 conflict
0x6034024e…442a
0x34b655…2a6f
2 touches
0 conflicts
0x62f5fc73…96fb
0x34b655…2a6f
2 touches
0 conflicts
0x6939e474…4256
0x34b655…2a6f
2 touches
0 conflicts
0x70b7b52e…7743
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity