← previous blocknext block →recent activity

Analyzing

Block #100,981,822

19 transactions · 18 stateful · 2026-09-01 07:24:46 UTC

Parallelism

79/100

Blocked

39%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,981,822  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xef3f5637…f47c

0x34b655…2a6f

4 touches
1 conflict

0xf87b7532…f93d

0x34b655…2a6f

4 touches
1 conflict

0xd17580f9…ece1

0x754704…b603

4 touches
1 conflict

0x0dd3d3cd…7281

0x34b655…2a6f

4 touches
1 conflict

0x1d9154e7…8821

0x34b655…2a6f

4 touches
1 conflict

0x6ca0994e…02ef

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 0xc824469a90…af6425

← previous block·next block →recent activity