← previous blocknext block →recent activity

Analyzing

Block #99,262,362

18 transactions · 18 stateful · 2026-08-26 06:53:25 UTC

Parallelism

83/100

Blocked

28%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,262,362  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

4 touches
1 conflict

0x97d6febb…31c6

0xa6afd3…d132

4 touches
1 conflict

0x3f2100d8…f9b5

0xa6afd3…d132

4 touches
1 conflict

0x1db5837f…1264

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xa366dc41…b2d8

0xa6afd3…d132

4 touches
1 conflict

0x8b780b26…f5ff

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

← previous block·next block →recent activity