← previous blocknext block →recent activity

Analyzing

Block #99,971,810

42 transactions · 35 stateful · 2026-08-28 18:38:22 UTC

Parallelism

71/100

Blocked

60%

Avg conflicts / tx

2.1

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #99,971,810  ·  42 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xd98b3c10…67b8

0x34b655…2a6f

22 touches
55 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x11258774…9892

0x2a68ba…90c5

10 touches
10 conflicts

0xdfa159d0…1576

0x065c9d…c394

10 touches
10 conflicts

0xa605468c…1bfc

0x2b46c0…1669

8 touches
6 conflicts

0xbb97db90…4c93

0xc8689a…ee79

8 touches
6 conflicts

0xcc4f1f14…aa5f

0x065c9d…c394

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 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

55 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity