← previous blocknext block →recent activity
Analyzing
Block #90,824,346
7 transactions · 6 stateful · 2026-07-27 16:53:21 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,824,346 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69a45f39…39aa
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x47e6eaf7…65eb
0x34b655…2a6f
2 touches
0 conflicts
0x6400e24b…7397
0x34b655…2a6f
2 touches
0 conflicts
0x70b7b52e…7743
0x34b655…2a6f
2 touches
0 conflicts
0x70b7b52e…7744
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
1 conflict on slot 0x69a45f39d6…c739aa
Audit this contract →
← previous block·next block →recent activity