← previous blocknext block →recent activity

Analyzing

Block #96,030,066

19 transactions · 16 stateful · 2026-08-14 21:55:57 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #96,030,066  ·  19 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

0xda457fb4…84a6

0x34b655…2a6f

6 touches
3 conflicts

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x41469894…598f

0x34b655…2a6f

4 touches
1 conflict

0x41469894…5990

0x34b655…2a6f

4 touches
1 conflict

0x66bdb4c2…7ea6

0x34b655…2a6f

4 touches
1 conflict

0x74e0d9d2…47d7

0x34b655…2a6f

4 touches
1 conflict

0x8c7eac39…f34d

0x34b655…2a6f

4 touches
1 conflict

0x9fd372a1…a959

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 0xda457fb40c…ff84a6

← previous block·next block →recent activity