← previous blocknext block →recent activity

Analyzing

Block #96,569,235

20 transactions · 16 stateful · 2026-08-16 19:08:07 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,569,235  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…000b

0x78999c…f371

10 touches
10 conflicts

0x00000000…000f

0x78999c…f371

10 touches
10 conflicts

0xe0659a3f…90d9

0x000000…a032

10 touches
10 conflicts

0x00000000…000b

0x754704…b603

10 touches
10 conflicts

0x34b1e500…7687

0x754704…b603

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6426

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

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: 0x78999cc9…3cf371

10 conflicts on slot 0x0000000000…00000b

← previous block·next block →recent activity