← previous blocknext block →recent activity
Analyzing
Block #95,204,101
18 transactions · 16 stateful · 2026-08-12 00:26:26 UTC
Parallelism
50/100
Blocked
56%
Avg conflicts / tx
2.11
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #95,204,101 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w48w59w610w711w814w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6518075e…2b17
0x2a68ba…90c5
18 touches
36 conflicts
0x84b20e5e…12de
0x40c49f…2af0
17 touches
36 conflicts
0x2b54cadb…4425
0xd18b7e…414b
16 touches
28 conflicts
0xa1087a5c…66c4
0x754704…b603
16 touches
28 conflicts
0x4df2af73…275a
0xd18b7e…414b
4 touches
1 conflict
0x3d9eb674…b3fb
0x754704…b603
4 touches
1 conflict
0x595233b5…c4aa
0x754704…b603
4 touches
1 conflict
0xa2478c84…6956
0x754704…b603
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
36 conflicts on slot 0x6518075e89…5f2b17
Audit this contract →
← previous block·next block →recent activity