← previous blocknext block →recent activity

Analyzing

Block #100,613,543

17 transactions · 16 stateful · 2026-08-31 00:31:49 UTC

Parallelism

82/100

Blocked

25%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,613,543  ·  17 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

0xa6d40b7f…2969

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x42522e76…2592

0x34b655…2a6f

4 touches
1 conflict

0xba9f9225…2ead

0x34b655…2a6f

4 touches
1 conflict

0xd03610a3…f998

0x34b655…2a6f

4 touches
1 conflict

0xe2de1aea…8024

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x556a9a7a…b0ae

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 0xa6d40b7f0d…ff2969

← previous block·next block →recent activity