← previous blocknext block →recent activity

Analyzing

Block #96,035,308

14 transactions · 13 stateful · 2026-08-14 22:22:22 UTC

Parallelism

71/100

Blocked

31%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #96,035,308  ·  14 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x931bd7a5…b6b9

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x120847e2…98c2

0x34b655…2a6f

4 touches
1 conflict

0x4c188934…158e

0x34b655…2a6f

4 touches
1 conflict

0x5e0b8bbe…377b

0x34b655…2a6f

4 touches
1 conflict

0x66bdb4c2…7ea6

0x34b655…2a6f

4 touches
1 conflict

0x74462c1e…84f3

0x34b655…2a6f

4 touches
1 conflict

0x8d4c0bb9…ccd3

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: Perpl

3 conflicts on slot 0x931bd7a585…f2b6b9

← previous block·next block →recent activity