← previous blocknext block →recent activity

Analyzing

Block #95,073,918

16 transactions · 13 stateful · 2026-08-11 13:31:35 UTC

Parallelism

81/100

Blocked

31%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,073,918  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x7de57974…f5ba

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xb5924647…4cf1

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x71161b8f…8d5a

0x34b655…2a6f

5 touches
3 conflicts

0x6c0e32fc…a6ca

0x34b655…2a6f

4 touches
1 conflict

0x70f537e8…399b

0x34b655…2a6f

4 touches
1 conflict

0x7b41d5cd…00e6

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

3 conflicts on slot 0x7de579746e…f0f5ba

← previous block·next block →recent activity