← previous blocknext block →recent activity

Analyzing

Block #96,609,751

21 transactions · 19 stateful · 2026-08-16 22:31:55 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

1.24

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #96,609,751  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x840d3ab7…c8c4

0x34b655…2a6f

10 touches
10 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

8 touches
6 conflicts

0x5b0ed476…61a6

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x9cafcdd0…4d69

0xd32edf…ff58

5 touches
3 conflicts

0x01078ee0…48e1

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

10 conflicts on slot 0x840d3ab7c3…edc8c4

← previous block·next block →recent activity