← previous blocknext block →recent activity
Analyzing
Block #91,409,885
21 transactions · 19 stateful · 2026-07-29 18:01:19 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,409,885 · 21 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
4w05w06w07w18w29w310w411w112w013w115w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724cd9ff…6684
0xe4f6e7…9657
10 touches
10 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
10 touches
10 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
10 touches
10 conflicts
0x00000000…0008
0x0ea966…0742
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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: 0xe4f6e757…919657
10 conflicts on slot 0x724cd9ff19…4c6684
Audit this contract →
← previous block·next block →recent activity