← previous blocknext block →recent activity

Analyzing

Block #95,528,131

17 transactions · 16 stateful · 2026-08-13 03:49:50 UTC

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,528,131  ·  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

0x08636046…e60f

0x34b655…2a6f

4 touches
1 conflict

0x0a57a2b8…3cdd

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00ddbbf2…4588

0x34b655…2a6f

2 touches
0 conflicts

0x071163fa…f7db

0x34b655…2a6f

2 touches
0 conflicts

0x13807d54…85db

0x34b655…2a6f

2 touches
0 conflicts

0x455a8076…be99

0x34b655…2a6f

2 touches
0 conflicts

0xb543d97e…cc3f

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x08636046fc…69e60f

← previous block·next block →recent activity