← previous blocknext block →recent activity
Analyzing
Block #90,802,887
18 transactions · 16 stateful · 2026-07-27 15:05:19 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,802,887 · 18 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
1w03w06w17w010w111w213w114w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0xfc13fc5f…a988
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8743e1ba…8331
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9a0c0bcb…0aff
0x34b655…2a6f
4 touches
1 conflict
0x9ff376ff…e8e4
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 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity