← previous blocknext block →recent activity
Analyzing
Block #94,195,520
10 transactions · 8 stateful · 2026-08-08 11:38:26 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,195,520 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w27w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb1863f9…afa9
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x12d867cc…b97c
0x34b655…2a6f
4 touches
1 conflict
0x16e75abd…f3ad
0x34b655…2a6f
4 touches
1 conflict
0x6b89ce6f…cc35
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 0xdb1863f9a8…e7afa9
Audit this contract →
← previous block·next block →recent activity