← previous blocknext block →recent activity

Analyzing

Block #95,471,932

24 transactions · 22 stateful · 2026-08-12 23:07:10 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

1.13

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #95,471,932  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xec7d120d…7084

0x34b655…2a6f

10 touches
10 conflicts

0x53f393fa…00b9

0x34b655…2a6f

10 touches
10 conflicts

0x369883e3…a449

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

6 touches
3 conflicts

0x1803586e…d149

0xa6afd3…d132

4 touches
1 conflict

0x3d6c26e5…1b45

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

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 0xec7d120df9…5d7084

← previous block·next block →recent activity