← previous blocknext block →recent activity
Analyzing
Block #94,250,845
10 transactions · 9 stateful · 2026-08-08 16:18:54 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,250,845 · 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
2w03w04w15w26w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f3a69a9…62d7
0x065c9d…c394
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x17c24c5b…471c
0x34b655…2a6f
4 touches
1 conflict
0x3d9eb674…b3fb
0x754704…b603
4 touches
1 conflict
0x54474915…9e0b
0x754704…b603
4 touches
1 conflict
0x2c66ecd1…f41d
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
3 conflicts on slot 0x0f3a69a9e2…1062d7
Audit this contract →
← previous block·next block →recent activity