← previous blocknext block →recent activity

Analyzing

Block #96,149,628

18 transactions · 17 stateful · 2026-08-15 07:57:24 UTC

Parallelism

61/100

Blocked

53%

Avg conflicts / tx

1.11

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #96,149,628  ·  18 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

0x4c188934…158e

0x34b655…2a6f

8 touches
6 conflicts

0xf5ea108a…dbf6

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x224d6800…4508

0x34b655…2a6f

4 touches
1 conflict

0x9a3463f0…0b73

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 0x4c18893450…c5158e

← previous block·next block →recent activity