← previous blocknext block →recent activity
Analyzing
Block #90,690,200
9 transactions · 9 stateful · 2026-07-27 05:38:24 UTC
Parallelism
44/100
Blocked
44%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,690,200 · 9 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f4727d…cdb7
0x34b655…2a6f
8 touches
6 conflicts
0x34933aba…06e4
0x34b655…2a6f
6 touches
3 conflicts
0x40aafdd2…46da
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x5b6af007…0f35
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x1653ea43…0082
0x34b655…2a6f
5 touches
3 conflicts
0x62dbeb4d…a388
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
6 conflicts on slot 0xf2f4727df6…a5cdb7
Audit this contract →
← previous block·next block →recent activity