← previous blocknext block →recent activity
Analyzing
Block #91,268,434
23 transactions · 22 stateful · 2026-07-29 06:08:34 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,268,434 · 23 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
1w02w14w05w16w07w19w210w011w314w315w218w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0xa01f2285…f16f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x369a943e…aef6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4807
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x5540f95607…2d69e8
Audit this contract →
← previous block·next block →recent activity