← previous blocknext block →recent activity

Analyzing

Block #95,743,517

22 transactions · 17 stateful · 2026-08-13 21:54:13 UTC

Parallelism

73/100

Blocked

53%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,743,517  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xe8146818…5583

0x34b655…2a6f

4 touches
1 conflict

0xf0d45ffd…89cf

0x34b655…2a6f

4 touches
1 conflict

0xfb67be15…a190

0x34b655…2a6f

4 touches
1 conflict

0x08636046…e60f

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

6 conflicts on slot 0x0a57a2b8cd…773cdd

← previous block·next block →recent activity