← previous blocknext block →recent activity
Analyzing
Block #90,025,903
9 transactions · 9 stateful · 2026-07-24 21:36:45 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,025,903 · 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
1w03w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x0cc65720…396c
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x1dd68810…d641
0x34b655…2a6f
2 touches
0 conflicts
0x1dd79365…4bab
0x34b655…2a6f
2 touches
0 conflicts
0x388633a0…86cd
0x34b655…2a6f
2 touches
0 conflicts
0x3bb1aafc…08d5
0x34b655…2a6f
2 touches
0 conflicts
0x40e67a5e…54a2
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity