← previous blocknext block →recent activity
Analyzing
Block #91,069,998
40 transactions · 34 stateful · 2026-07-28 13:30:01 UTC
Parallelism
88/100
Blocked
44%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,069,998 · 40 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
2w03w14w25w38w012w013w115w216w319w022w124w126w228w430w031w133w134w235w036w137w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
10 touches
10 conflicts
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x21898044…a071
0x065c9d…c394
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0xc824469a…6425
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: 0x681e908b…e1ae09
10 conflicts on slot 0x0d622e34f9…000000
Audit this contract →
← previous block·next block →recent activity