← previous blocknext block →recent activity

Analyzing

Block #96,600,216

23 transactions · 18 stateful · 2026-08-16 21:43:57 UTC

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

0.74

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #96,600,216  ·  23 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

0x2d651956…12e8

0x34b655…2a6f

10 touches
10 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0x4356c9e6…9bf4

0x3bd359…433a

4 touches
1 conflict

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0xdb3937e8…23cb

0x34b655…2a6f

4 touches
1 conflict

0xdf0b4e17…ccd8

0x34b655…2a6f

4 touches
1 conflict

0xe8e9df5e…dc09

0x34b655…2a6f

4 touches
1 conflict

0x34cdb3c2…96d2

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