← previous blocknext block →recent activity
Analyzing
Block #99,329,841
18 transactions · 18 stateful · 2026-08-26 12:32:51 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,329,841 · 18 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
2w03w14w25w06w110w212w314w316w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x065ff70b…356d
0x40c49f…2af0
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xe317a5c7…6ddf
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa9af9157…5a6e
0x34b655…2a6f
4 touches
1 conflict
0xac389ba9…8b45
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
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: 0x40c49f17…d22af0
3 conflicts on slot 0x065ff70bfe…b9356d
Audit this contract →
← previous block·next block →recent activity