← previous blocknext block →recent activity

Analyzing

Block #96,548,399

11 transactions · 9 stateful · 2026-08-16 17:23:19 UTC

Parallelism

64/100

Blocked

44%

Avg conflicts / tx

0.73

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #96,548,399  ·  11 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

0x1b287091…65ac

0x34b655…2a6f

8 touches
6 conflicts

0x818e1296…f4d7

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xe0c7e023…2a08

0x34b655…2a6f

4 touches
1 conflict

0x33967383…de4d

0x34b655…2a6f

4 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0xa4e9800f…4ab0

0x34b655…2a6f

4 touches
1 conflict

0xac0b4a08…faae

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 0x1b287091ad…e465ac

← previous block·next block →recent activity