← previous blocknext block →recent activity

Analyzing

Block #97,355,817

17 transactions · 16 stateful · 2026-08-19 13:25:06 UTC

Parallelism

76/100

Blocked

44%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,355,817  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xe7fbfc54…23cd

0x34b655…2a6f

6 touches
3 conflicts

0x42041fec…bd86

0x754704…b603

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x5d863b2f…bd28

0x34b655…2a6f

4 touches
1 conflict

0xba9f9225…2ead

0x34b655…2a6f

4 touches
1 conflict

0xd597209e…9800

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 0xc824469a90…af6425

← previous block·next block →recent activity