← previous blocknext block →recent activity

Analyzing

Block #95,648,132

20 transactions · 18 stateful · 2026-08-13 13:53:25 UTC

Parallelism

45/100

Blocked

67%

Avg conflicts / tx

1.2

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #95,648,132  ·  20 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x66d5e476…8a1f

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0x0f2d78b1…7363

0x34b655…2a6f

6 touches
3 conflicts

0x680fdd59…e84d

0x34b655…2a6f

4 touches
1 conflict

0x80467952…c46f

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 0xca841faae5…71486a

← previous block·next block →recent activity