← previous blocknext block →recent activity

Analyzing

Block #95,656,373

20 transactions · 17 stateful · 2026-08-13 14:34:52 UTC

Parallelism

80/100

Blocked

35%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,656,373  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xb39cb1d8…effa

0x34b655…2a6f

6 touches
3 conflicts

0x19cbeea8…ecf3

0x34b655…2a6f

4 touches
1 conflict

0x213a54fa…c85f

0x34b655…2a6f

4 touches
1 conflict

0x38bdc5d3…a632

0x34b655…2a6f

4 touches
1 conflict

0x38befc08…20c8

0x34b655…2a6f

4 touches
1 conflict

0x3a37aad1…720f

0x34b655…2a6f

4 touches
1 conflict

0x43fd3667…094b

0x34b655…2a6f

4 touches
1 conflict

0x71ba83aa…be81

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 0xb39cb1d8c6…28effa

← previous block·next block →recent activity