← previous blocknext block →recent activity

Analyzing

Block #96,035,763

20 transactions · 16 stateful · 2026-08-14 22:24:39 UTC

Parallelism

65/100

Blocked

56%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #96,035,763  ·  20 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

0x0f2d78b1…7363

0x34b655…2a6f

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x931bd7a5…b6b9

0x34b655…2a6f

6 touches
3 conflicts

0x3beb6746…2293

0x34b655…2a6f

6 touches
3 conflicts

0xb2751758…36a0

0x34b655…2a6f

6 touches
3 conflicts

0x7ea60711…6098

0x34b655…2a6f

4 touches
2 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

4 touches
1 conflict

0xda3eb3c3…9d60

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 0x0f2d78b1bb…5e7363

← previous block·next block →recent activity