← previous blocknext block →recent activity

Analyzing

Block #99,588,389

18 transactions · 17 stateful · 2026-08-27 10:17:36 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,588,389  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x395bbb78…0fa0

0x34b655…2a6f

4 touches
1 conflict

0x3fff7ccd…5a48

0x34b655…2a6f

4 touches
1 conflict

0x4ac4a2c2…2707

0x34b655…2a6f

4 touches
1 conflict

0x4f2778a8…8415

0x34b655…2a6f

4 touches
1 conflict

0x51d2cc81…9a62

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 0xca841faae5…71486a

← previous block·next block →recent activity