← previous blocknext block →recent activity

Analyzing

Block #96,115,298

18 transactions · 17 stateful · 2026-08-15 05:04:40 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.61

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #96,115,298  ·  18 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

0xafb8e71e…9285

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x424934c8…f2f1

0x34b655…2a6f

6 touches
3 conflicts

0x07e62691…ad33

0x34b655…2a6f

6 touches
3 conflicts

0xe9452241…95a3

0x34b655…2a6f

4 touches
1 conflict

0x2015205e…6b1d

0x34b655…2a6f

4 touches
1 conflict

0x37674bd8…8f35

0x34b655…2a6f

4 touches
1 conflict

0xd5e10fed…6daa

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 0xafb8e71eb0…ec9285

← previous block·next block →recent activity