← previous blocknext block →recent activity
Analyzing
Block #90,514,356
10 transactions · 10 stateful · 2026-07-26 14:53:49 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,514,356 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2a6942f…e69d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x481b500f…7ef3
0x34b655…2a6f
4 touches
1 conflict
0x4bd79f91…4d5b
0x34b655…2a6f
4 touches
1 conflict
0x02ecd54c…1f6c
0x34b655…2a6f
2 touches
0 conflicts
0x0b8d3b82…6fe7
0x34b655…2a6f
2 touches
0 conflicts
0x1960b414…14a6
0x34b655…2a6f
2 touches
0 conflicts
0x1c097b81…0164
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 0xe2a6942fa9…f6e69d
Audit this contract →
← previous block·next block →recent activity