← previous blocknext block →recent activity

Analyzing

Block #97,711,062

20 transactions · 19 stateful · 2026-08-20 19:49:14 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

0.85

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,711,062  ·  20 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

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0x72d065cf…1dd1

0x34b655…2a6f

4 touches
1 conflict

0xc2e8bece…67d9

0x34b655…2a6f

4 touches
1 conflict

0xf5938cff…6608

0x34b655…2a6f

4 touches
1 conflict

0x7bdccbcd…6bed

0x40c49f…2af0

4 touches
1 conflict

0xc824469a…6425

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

6 conflicts on slot 0xec7d120df9…5d7084

← previous block·next block →recent activity