← previous blocknext block →recent activity

Analyzing

Block #97,559,632

28 transactions · 26 stateful · 2026-08-20 06:56:10 UTC

Parallelism

71/100

Blocked

62%

Avg conflicts / tx

1.68

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #97,559,632  ·  28 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x00000000…0002

0x103de0…bb55

16 touches
28 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0x94dabb65…43a3

0x34b655…2a6f

10 touches
10 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

6 touches
3 conflicts

0x2b122179…55a7

0x065c9d…c394

5 touches
3 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: 0x103de0b5…25bb55

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity