← previous blocknext block →recent activity
Analyzing
Block #94,752,424
25 transactions · 16 stateful · 2026-08-10 10:33:30 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,752,424 · 25 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
1w08w19w010w211w315w116w217w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xeae24c…0be0
6 touches
3 conflicts
0x19c2c87b…cee5
0xd32edf…ff58
5 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity