← previous blocknext block →recent activity

Analyzing

Block #100,618,558

19 transactions · 18 stateful · 2026-08-31 00:57:03 UTC

Parallelism

79/100

Blocked

39%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,618,558  ·  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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x5311f864…0984

0x754704…b603

4 touches
1 conflict

0x10ca7c55…c28d

0x34b655…2a6f

4 touches
1 conflict

0x065ff70b…356d

0x40c49f…2af0

4 touches
1 conflict

0x3f81bcfb…2905

0x40c49f…2af0

4 touches
1 conflict

0x41469894…598f

0x34b655…2a6f

4 touches
1 conflict

0x41469894…5990

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity