← previous blocknext block →recent activity

Analyzing

Block #95,474,456

17 transactions · 16 stateful · 2026-08-12 23:19:52 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,474,456  ·  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

0xbd96f96f…5843

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0xb808b9ed…2865

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0x3fffbdea…e670

0x34b655…2a6f

2 touches
0 conflicts

0x4a5956ef…e226

0x34b655…2a6f

2 touches
0 conflicts

0x71e1dee6…d11b

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 0xbd96f96f0a…875843

← previous block·next block →recent activity