← previous blocknext block →recent activity

Analyzing

Block #97,709,624

19 transactions · 18 stateful · 2026-08-20 19:41:58 UTC

Parallelism

89/100

Blocked

11%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #97,709,624  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x0bc43347…93d4

0x34b655…2a6f

4 touches
1 conflict

0xe429e4c9…9510

0x34b655…2a6f

4 touches
1 conflict

0xfaab1754…53be

0x34b655…2a6f

4 touches
1 conflict

0x5d7e0e69…e6d2

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

2 touches
0 conflicts

0x7de57974…f5ba

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0x0bc433477d…9e93d4

← previous block·next block →recent activity