← previous blocknext block →recent activity
Analyzing
Block #99,183,878
34 transactions · 26 stateful · 2026-08-26 00:18:27 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,183,878 · 34 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w212w213w316w017w124w031w032w133w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38b5b2ce…c5bb
0xfa32f9…f3f0
8 touches
6 conflicts
0x99f666e3…b2a2
0x3bd359…433a
8 touches
6 conflicts
0x9194f4a3…10b8
0x754704…b603
8 touches
6 conflicts
0x00000000…0000
0xfa32f9…f3f0
8 touches
6 conflicts
0x00000000…0001
0xfa32f9…f3f0
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xb538c6fa…9ae7
0x1b6862…e19c
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: 0xfa32f9ec…fef3f0
6 conflicts on slot 0x38b5b2ceac…4cc5bb
Audit this contract →
← previous block·next block →recent activity