← previous blocknext block →recent activity

Analyzing

Block #95,075,770

17 transactions · 17 stateful · 2026-08-11 13:40:55 UTC

Parallelism

82/100

Blocked

35%

Avg conflicts / tx

0.53

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,075,770  ·  17 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

0x40a9339c…6571

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00966e54…7d1d

0x34b655…2a6f

4 touches
1 conflict

0x07c60d76…fe95

0x34b655…2a6f

4 touches
1 conflict

0x0f2d78b1…7363

0x34b655…2a6f

4 touches
1 conflict

0x2aea13df…4958

0x34b655…2a6f

4 touches
1 conflict

0x3439dfbc…0d03

0x34b655…2a6f

4 touches
1 conflict

0x34806b11…bdf5

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 0x40a9339c51…376571

← previous block·next block →recent activity