← previous blocknext block →recent activity

Analyzing

Block #96,266,525

18 transactions · 17 stateful · 2026-08-15 17:45:20 UTC

Parallelism

72/100

Blocked

47%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,266,525  ·  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

0x66bdb4c2…7ea6

0x34b655…2a6f

6 touches
3 conflicts

0x5540f956…69e8

0x065c9d…c394

6 touches
3 conflicts

0xaf90b3f4…5873

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

6 touches
3 conflicts

0xc124f6b3…a94e

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0x1045386d…cb86

0x1b6862…e19c

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 0x66bdb4c268…a97ea6

← previous block·next block →recent activity