← previous blocknext block →recent activity

Analyzing

Block #96,111,835

17 transactions · 15 stateful · 2026-08-15 04:47:14 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.88

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,111,835  ·  17 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

0x53f393fa…00b9

0x34b655…2a6f

8 touches
6 conflicts

0x16f8e14a…f6e4

0x34b655…2a6f

4 touches
1 conflict

0x1a5d321d…a474

0x34b655…2a6f

4 touches
1 conflict

0x224d6800…4508

0x34b655…2a6f

4 touches
1 conflict

0x31b39922…1e65

0x34b655…2a6f

4 touches
1 conflict

0x31b39922…1e66

0x34b655…2a6f

4 touches
1 conflict

0x455adb1f…1e83

0x34b655…2a6f

4 touches
1 conflict

0x4b80417b…75c3

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

6 conflicts on slot 0x53f393fafd…2a00b9

← previous block·next block →recent activity