← previous blocknext block →recent activity

Analyzing

Block #96,797,860

21 transactions · 19 stateful · 2026-08-17 14:18:01 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.62

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #96,797,860  ·  21 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

0x5bbda264…7dd0

0x34b655…2a6f

6 touches
3 conflicts

0x2491d756…b71c

0xa6afd3…d132

6 touches
3 conflicts

0xfbe6a366…8ca1

0x34b655…2a6f

6 touches
3 conflicts

0x6f6fc26c…3e34

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x8cd684d0…c3cb

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…7214

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…7215

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 0x5bbda26465…717dd0

← previous block·next block →recent activity