← previous blocknext block →recent activity

Analyzing

Block #96,604,684

17 transactions · 17 stateful · 2026-08-16 22:06:26 UTC

Parallelism

71/100

Blocked

41%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,604,684  ·  17 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

0x2d651956…12e8

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x4caa7900…fd2e

0x34b655…2a6f

4 touches
1 conflict

0x5a0a2b03…ac50

0x34b655…2a6f

4 touches
1 conflict

0x5bbda264…7dd0

0x34b655…2a6f

4 touches
1 conflict

0x5bbda264…7dd1

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

10 conflicts on slot 0x2d65195682…4112e8

← previous block·next block →recent activity