← previous blocknext block →recent activity
Analyzing
Block #90,838,193
11 transactions · 11 stateful · 2026-07-27 18:03:01 UTC
Parallelism
55/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,838,193 · 11 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
2w03w14w05w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe2e52e46…0894
0x34b655…2a6f
4 touches
1 conflict
0xf3383813…4a0c
0x34b655…2a6f
4 touches
1 conflict
0xf71db89c…d147
0x34b655…2a6f
4 touches
1 conflict
0x0b0611f7…e63a
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
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
1 conflict on slot 0x9fd372a13e…ada959
Audit this contract →
← previous block·next block →recent activity