← previous blocknext block →recent activity
Analyzing
Block #94,751,516
13 transactions · 12 stateful · 2026-08-10 10:28:52 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,751,516 · 13 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
1w06w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x29e7f879…1281
0x065c9d…c394
2 touches
0 conflicts
0x3ab22786…9f66
0x065c9d…c394
2 touches
0 conflicts
0x3d889ae9…c6f0
0x065c9d…c394
2 touches
0 conflicts
0x552bfda5…3509
0x065c9d…c394
2 touches
0 conflicts
0x61783c1c…15a7
0x065c9d…c394
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
1 conflict on slot 0xb33ff82315…a81188
Audit this contract →
← previous block·next block →recent activity