← previous blocknext block →recent activity

Analyzing

Block #99,248,527

17 transactions · 16 stateful · 2026-08-26 05:43:44 UTC

Parallelism

82/100

Blocked

44%

Avg conflicts / tx

0.71

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,248,527  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xf5b5f7…6d70

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0xf91ef75c…1669

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

3 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity