← previous blocknext block →recent activity

Analyzing

Block #96,611,264

18 transactions · 15 stateful · 2026-08-16 22:39:31 UTC

Parallelism

67/100

Blocked

60%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #96,611,264  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xe5a9274d…78d7

0x34b655…2a6f

6 touches
3 conflicts

0xca2926e0…61b5

0x34b655…2a6f

6 touches
3 conflicts

0x840d3ab7…c8c4

0x34b655…2a6f

4 touches
1 conflict

0xa558e115…fc88

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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 0xca841faae5…71486a

← previous block·next block →recent activity