← previous blocknext block →recent activity

Analyzing

Block #99,819,690

19 transactions · 17 stateful · 2026-08-28 05:51:07 UTC

Parallelism

74/100

Blocked

41%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,819,690  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf15273a1…2c52

0x34b655…2a6f

8 touches
6 conflicts

0xafe81a7b…bcbf

0x34b655…2a6f

6 touches
3 conflicts

0x04b326e7…a0b8

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x53ca1284…cb2c

0x34b655…2a6f

6 touches
3 conflicts

0x3c67d31e…3dbe

0x34b655…2a6f

6 touches
3 conflicts

0xd96b70d8…e435

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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 0xf15273a148…932c52

← previous block·next block →recent activity