← previous blocknext block →recent activity

Analyzing

Block #97,666,133

20 transactions · 20 stateful · 2026-08-20 15:59:52 UTC

Parallelism

75/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,666,133  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc2e8bece…67d9

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x9db64d13…fb98

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xdf092a40…d94d

0x34b655…2a6f

4 touches
1 conflict

0xf9e13c70…d888

0x34b655…2a6f

4 touches
1 conflict

0x0c089c67…f76c

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

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 0xc2e8beced0…cb67d9

← previous block·next block →recent activity