← previous blocknext block →recent activity

Analyzing

Block #96,447,883

18 transactions · 15 stateful · 2026-08-16 08:57:27 UTC

Parallelism

72/100

Blocked

60%

Avg conflicts / tx

0.89

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,447,883  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x7de57974…f5ba

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x3f42244d…7d8b

0x34b655…2a6f

4 touches
1 conflict

0x5484fc7f…a8d8

0x34b655…2a6f

4 touches
1 conflict

0x5f447bf3…57c7

0x34b655…2a6f

4 touches
1 conflict

0x5f56ffe5…09c0

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 0x7de579746e…f0f5ba

← previous block·next block →recent activity