← previous blocknext block →recent activity

Analyzing

Block #95,269,265

22 transactions · 21 stateful · 2026-08-12 06:02:58 UTC

Parallelism

68/100

Blocked

52%

Avg conflicts / tx

1.73

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,269,265  ·  22 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

0x0a57a2b8…3cdd

0x34b655…2a6f

12 touches
15 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

10 touches
10 conflicts

0x95c47f03…f1bb

0x34b655…2a6f

8 touches
6 conflicts

0xf0d45ffd…89cf

0x34b655…2a6f

8 touches
6 conflicts

0x6baed27e…26fa

0x34b655…2a6f

6 touches
3 conflicts

0x736bfd85…2594

0x34b655…2a6f

6 touches
3 conflicts

0xeee4efbb…48c3

0x34b655…2a6f

6 touches
3 conflicts

0x66d5e476…8a1f

0x34b655…2a6f

6 touches
3 conflicts

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

15 conflicts on slot 0x0a57a2b8cd…773cdd

← previous block·next block →recent activity