← previous blocknext block →recent activity
Analyzing
Block #90,822,758
15 transactions · 13 stateful · 2026-07-27 16:45:22 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,822,758 · 15 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
1w02w13w05w110w111w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26d1c221…4d2a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf85fbefc…6825
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x41dc2b7f…1af1
0x34b655…2a6f
2 touches
0 conflicts
0x41dc2b7f…1af2
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 0x26d1c221d7…ef4d2a
Audit this contract →
← previous block·next block →recent activity