← previous blocknext block →recent activity
Analyzing
Block #90,799,963
19 transactions · 14 stateful · 2026-07-27 14:50:36 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,799,963 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w19w010w111w212w314w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe25fa437…1f16
0x34b655…2a6f
6 touches
3 conflicts
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0x836544ae…79e6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2fe57c3f…8f29
0x34b655…2a6f
4 touches
1 conflict
0x3ea25e92…a36d
0x34b655…2a6f
4 touches
1 conflict
0x428b6e5b…8909
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
3 conflicts on slot 0xe25fa4370e…0c1f16
Audit this contract →
← previous block·next block →recent activity