← previous blocknext block →recent activity

Analyzing

Block #100,146,392

31 transactions · 19 stateful · 2026-08-29 09:17:31 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,146,392  ·  31 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

0x7dae0b6c…a3ea

0x34b655…2a6f

8 touches
6 conflicts

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0xe5b70be7…07b7

0x34b655…2a6f

8 touches
6 conflicts

0x6b267bdf…b173

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4fce3905…6f4f

0x34b655…2a6f

4 touches
1 conflict

0x61571888…b392

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0x7dae0b6cdb…43a3ea

← previous block·next block →recent activity