← previous blocknext block →recent activity
Analyzing
Block #99,329,393
26 transactions · 19 stateful · 2026-08-26 12:30:35 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,329,393 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w06w17w28w010w118w221w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xcc947020…64da
0x34b655…2a6f
4 touches
1 conflict
0x8a02d049…f481
0x34b655…2a6f
4 touches
1 conflict
0x5cb7cd69…7da1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
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: 0xf5b5f7f8…a36d70
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity