← previous blocknext block →recent activity

Analyzing

Block #97,628,723

21 transactions · 20 stateful · 2026-08-20 12:45:45 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

1.14

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,628,723  ·  21 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

0x00000000…0002

0x103de0…bb55

14 touches
21 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xdfa159d0…1576

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xcc4f1f14…aa5f

0x065c9d…c394

4 touches
1 conflict

0x8e06e67a…dfee

0x065c9d…c394

3 touches
1 conflict

0x0fc41e7b…6831

0x98dc6e…8633

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

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity