← previous blocknext block →recent activity
Analyzing
Block #94,742,229
8 transactions · 8 stateful · 2026-08-10 09:41:36 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,742,229 · 8 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5101fa65…ee9b
0x065c9d…c394
4 touches
1 conflict
0x63ab0974…1a81
0x065c9d…c394
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa7c486f5…f67c
0x065c9d…c394
3 touches
1 conflict
0x611040e6…e995
0x065c9d…c394
3 touches
1 conflict
0x27716cd8…a360
0x065c9d…c394
3 touches
1 conflict
0xa7c486f5…f67d
0x065c9d…c394
3 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
1 conflict on slot 0x5101fa65b0…5bee9b
Audit this contract →
← previous block·next block →recent activity