← previous blocknext block →recent activity
Analyzing
Block #91,088,141
29 transactions · 23 stateful · 2026-07-28 15:01:21 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,088,141 · 29 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
1w02w13w26w07w312w014w116w019w021w124w225w326w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6bd849a…5597
0x2a68ba…90c5
6 touches
3 conflicts
0x452574b3…11e9
0xd32edf…ff58
5 touches
3 conflicts
0x0590f32c…8423
0xa6afd3…d132
5 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x511f46a7…eda8
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0xd6bd849ae7…7c5597
Audit this contract →
← previous block·next block →recent activity