← previous blocknext block →recent activity
Analyzing
Block #90,210,853
23 transactions · 22 stateful · 2026-07-25 13:11:50 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,210,853 · 23 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
8w010w011w112w213w315w117w020w322w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae085366…fa10
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x803eb45d…00bd
0x34b655…2a6f
6 touches
3 conflicts
0x34036ecb…2132
0x34b655…2a6f
6 touches
3 conflicts
0x7e1d87b8…291c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x87ab06cc…147e
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xae085366d1…3cfa10
Audit this contract →
← previous block·next block →recent activity