← previous blocknext block →recent activity
Analyzing
Block #99,279,176
14 transactions · 13 stateful · 2026-08-26 08:18:00 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,279,176 · 14 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
1w04w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36dcf7f4…c37b
0x065c9d…c394
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x56d5dcdf…b5b6
0x065c9d…c394
3 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x997ccc40…4dfd
0x3bd359…433a
2 touches
0 conflicts
0xe2745681…ff50
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x52c17a…f6f4
2 touches
0 conflicts
0x1e079abd…bd95
0x52c17a…f6f4
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 0x36dcf7f4b5…9dc37b
Audit this contract →
← previous block·next block →recent activity