← previous blocknext block →recent activity

Analyzing

Block #96,372,129

15 transactions · 15 stateful · 2026-08-16 02:36:29 UTC

Parallelism

80/100

Blocked

27%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #96,372,129  ·  15 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

0xe2f494fd…bd0a

0x34b655…2a6f

6 touches
3 conflicts

0x11431f9d…42c5

0x34b655…2a6f

4 touches
1 conflict

0x17935a8f…a796

0x34b655…2a6f

4 touches
1 conflict

0x2832416b…e1b8

0x34b655…2a6f

4 touches
1 conflict

0x344bc09a…942f

0x34b655…2a6f

4 touches
1 conflict

0x34d95d94…3a16

0x34b655…2a6f

4 touches
1 conflict

0x3727225e…a3cf

0x34b655…2a6f

4 touches
1 conflict

0x3c7c65d0…0b52

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 0xe2f494fd05…43bd0a

← previous block·next block →recent activity