← previous blocknext block →recent activity
Analyzing
Block #90,802,317
18 transactions · 16 stateful · 2026-07-27 15:02:27 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,802,317 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w27w38w410w116w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ce18f62…c25a
0x34b655…2a6f
6 touches
3 conflicts
0xa3f6f7c8…2436
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xe4a46469…d553
0x40c49f…2af0
4 touches
1 conflict
0xe3471350…0bcf
0x34b655…2a6f
4 touches
1 conflict
0xfcdb5918…2b49
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x1d7bc23d…2bea
0x40c49f…2af0
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 0x0ce18f62c6…60c25a
Audit this contract →
← previous block·next block →recent activity