← previous blocknext block →recent activity

Analyzing

Block #97,386,357

31 transactions · 24 stateful · 2026-08-19 16:08:09 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.68

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,386,357  ·  31 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xec7d120d…7084

0x34b655…2a6f

10 touches
10 conflicts

0xbb56619b…1b27

0x34b655…2a6f

8 touches
6 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0xd4230a60…bd13

0x34b655…2a6f

4 touches
1 conflict

0x041210e0…a00c

0x34b655…2a6f

4 touches
1 conflict

0x037a4023…1f5a

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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 0xec7d120df9…5d7084

← previous block·next block →recent activity