← previous blocknext block →recent activity
Analyzing
Block #90,209,952
17 transactions · 17 stateful · 2026-07-25 13:07:18 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,209,952 · 17 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
1w03w04w15w26w37w18w112w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0000
0xae3e24…7d91
6 touches
3 conflicts
0xfc101022…14d9
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0003
0xae3e24…7d91
6 touches
3 conflicts
0xf39f594c…4e93
0xfd9758…7777
6 touches
3 conflicts
0x12711b58…80f3
0x384275…7777
4 touches
1 conflict
0x1ad0dd99…7fab
0x384275…7777
4 touches
1 conflict
0x1167512f…b162
0x3bd359…433a
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity