← previous blocknext block →recent activity

Analyzing

Block #95,974,036

22 transactions · 19 stateful · 2026-08-14 17:14:00 UTC

Parallelism

68/100

Blocked

37%

Avg conflicts / tx

0.77

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,974,036  ·  22 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

0x53f393fa…00b9

0x34b655…2a6f

10 touches
10 conflicts

0x19e69334…a345

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x410b84ab…1dbc

0x34b655…2a6f

4 touches
1 conflict

0x948e8d20…a8df

0x34b655…2a6f

4 touches
1 conflict

0xa5a8ffca…8de2

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 0x53f393fafd…2a00b9

← previous block·next block →recent activity