← previous blocknext block →recent activity
Analyzing
Block #94,797,403
24 transactions · 20 stateful · 2026-08-10 14:19:56 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,797,403 · 24 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
1w02w13w06w19w211w016w317w419w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4f80979…4d71
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x9c747ff4…2cb8
0xd32edf…ff58
5 touches
3 conflicts
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0xcac586cc…8d20
0x065c9d…c394
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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
6 conflicts on slot 0xa4f8097941…fd4d71
Audit this contract →
← previous block·next block →recent activity