← previous blocknext block →recent activity

Analyzing

Block #99,180,817

27 transactions · 25 stateful · 2026-08-26 00:03:03 UTC

Parallelism

67/100

Blocked

36%

Avg conflicts / tx

0.93

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #99,180,817  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xb409e204…89ac

0x34b655…2a6f

6 touches
3 conflicts

0x4984f7be…d515

0x34b655…2a6f

4 touches
1 conflict

0x6c60fbcf…8744

0x34b655…2a6f

4 touches
1 conflict

0x72254e2e…3dea

0x34b655…2a6f

4 touches
1 conflict

0x7506443a…4820

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity