← previous blocknext block →recent activity
Analyzing
Block #90,041,466
14 transactions · 14 stateful · 2026-07-24 22:55:11 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,041,466 · 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
1w02w13w05w06w17w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba6f6560…e7ea
0x34b655…2a6f
6 touches
3 conflicts
0xb176789b…c34b
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xca5ce0d1…691f
0x34b655…2a6f
4 touches
1 conflict
0x06c980ab…5577
0x34b655…2a6f
4 touches
1 conflict
0x1321736a…43e3
0x34b655…2a6f
4 touches
1 conflict
0x2101287f…3f9d
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 0xba6f65601c…60e7ea
Audit this contract →
← previous block·next block →recent activity