← previous blocknext block →recent activity

Analyzing

Block #96,084,061

14 transactions · 14 stateful · 2026-08-15 02:27:34 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #96,084,061  ·  14 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

0x977f8f24…61ae

0x34b655…2a6f

6 touches
3 conflicts

0xa5a8ffca…8de2

0x34b655…2a6f

6 touches
3 conflicts

0xbb3b1855…cd23

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xec7d120d…7084

0x34b655…2a6f

4 touches
1 conflict

0x713ba679…f953

0x34b655…2a6f

4 touches
1 conflict

0xf9874e36…beed

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 0x977f8f24f7…a861ae

← previous block·next block →recent activity