← previous blocknext block →recent activity

Analyzing

Block #99,870,422

25 transactions · 23 stateful · 2026-08-28 10:07:29 UTC

Parallelism

72/100

Blocked

48%

Avg conflicts / tx

1.08

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,870,422  ·  25 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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd376181c…f040

0x34b655…2a6f

6 touches
3 conflicts

0xe7ad475a…0e41

0x34b655…2a6f

6 touches
3 conflicts

0x295780b7…d2d1

0x34b655…2a6f

6 touches
3 conflicts

0x67c7e95e…8301

0x34b655…2a6f

4 touches
1 conflict

0x68dfc6ca…56ac

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity