← previous blocknext block →recent activity

Analyzing

Block #99,626,937

17 transactions · 17 stateful · 2026-08-27 13:35:42 UTC

Parallelism

53/100

Blocked

47%

Avg conflicts / tx

1.18

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,626,937  ·  17 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x2c24528e…0152

0x851145…3f07

4 touches
1 conflict

0x8d5fc820…1750

0x34b655…2a6f

4 touches
1 conflict

0xb2d8af24…4750

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

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

10 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity