← previous blocknext block →recent activity

Analyzing

Block #97,385,559

20 transactions · 18 stateful · 2026-08-19 16:02:13 UTC

Parallelism

80/100

Blocked

39%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,385,559  ·  20 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

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0xffc2f21e…b393

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x103de0…bb55

4 touches
1 conflict

0x4431d60f…709b

0x34b655…2a6f

4 touches
1 conflict

0x81501297…c4b7

0x34b655…2a6f

4 touches
1 conflict

0x85eb1316…bb9e

0x34b655…2a6f

4 touches
1 conflict

0x9a64d6c3…6d1d

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

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 0xb3fb9fb561…7664db

← previous block·next block →recent activity