← previous blocknext block →recent activity
Analyzing
Block #91,439,834
20 transactions · 19 stateful · 2026-07-29 20:32:56 UTC
Parallelism
90/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,439,834 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w07w010w112w113w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x92115abd…ad76
0x34b655…2a6f
4 touches
1 conflict
0xa9a49465…0424
0x34b655…2a6f
4 touches
1 conflict
0x1a86a19b…b4e8
0x34b655…2a6f
2 touches
0 conflicts
0x1cd97124…bea5
0x34b655…2a6f
2 touches
0 conflicts
0x282b6dca…fc80
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity