← previous blocknext block →recent activity

Analyzing

Block #96,664,162

16 transactions · 14 stateful · 2026-08-17 03:05:34 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #96,664,162  ·  16 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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x6bdb9869…7558

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xc8c615d4…5da3

0x34b655…2a6f

6 touches
3 conflicts

0xd192f4ed…d7ec

0x34b655…2a6f

6 touches
3 conflicts

0xdade69ff…a4a4

0x34b655…2a6f

6 touches
3 conflicts

0x37e18b60…a96b

0x34b655…2a6f

6 touches
3 conflicts

0x08e8f2c9…a11a

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 0x482471adbb…39122f

← previous block·next block →recent activity