← previous blocknext block →recent activity
Analyzing
Block #99,184,076
37 transactions · 32 stateful · 2026-08-26 00:19:27 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.97
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,184,076 · 37 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w29w011w312w413w114w216w117w119w021w126w529w232w633w735w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x348fda08…7e96
0x065c9d…c394
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xba38536d…2b7d
0x065c9d…c394
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity