← previous blocknext block →recent activity
Analyzing
Block #99,076,167
30 transactions · 24 stateful · 2026-08-25 15:16:07 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,076,167 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w18w09w210w311w212w015w319w121w423w225w527w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0x47b807a2…3307
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0xa50e1ac0…9b22
0x065c9d…c394
5 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
6 conflicts on slot 0x1125877469…519892
Audit this contract →
← previous block·next block →recent activity