← previous blocknext block →recent activity

Analyzing

Block #99,977,569

24 transactions · 22 stateful · 2026-08-28 19:07:23 UTC

Parallelism

75/100

Blocked

41%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,977,569  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x451e482b…7e7d

0x34b655…2a6f

6 touches
3 conflicts

0xfb14d7f1…e509

0x34b655…2a6f

6 touches
3 conflicts

0x50c61506…343f

0x34b655…2a6f

4 touches
1 conflict

0xaa74a1a7…02a3

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa23619a7…40e4

0x3bd359…433a

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: Perpl

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity