← previous blocknext block →recent activity

Analyzing

Block #97,565,363

23 transactions · 19 stateful · 2026-08-20 07:25:24 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,565,363  ·  23 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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x20492d53…80f9

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x21ca7579…1a1e

0x34b655…2a6f

4 touches
1 conflict

0x30dac28a…5edd

0x34b655…2a6f

4 touches
1 conflict

0x3f5831e5…02b2

0x34b655…2a6f

4 touches
1 conflict

0x8a02d049…f481

0x34b655…2a6f

4 touches
1 conflict

0x94dabb65…43a3

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

6 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity