← previous blocknext block →recent activity

Analyzing

Block #95,152,827

20 transactions · 16 stateful · 2026-08-11 20:08:32 UTC

Parallelism

70/100

Blocked

50%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,152,827  ·  20 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

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

4 touches
1 conflict

0x0e182b40…1f35

0x34b655…2a6f

4 touches
1 conflict

0x37ce0b10…39b8

0x34b655…2a6f

4 touches
1 conflict

0x42e917f7…ed8c

0x34b655…2a6f

4 touches
1 conflict

0x734ee320…caae

0x34b655…2a6f

4 touches
1 conflict

0x77aa49e7…df90

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity