← previous blocknext block →recent activity

Analyzing

Block #101,817,940

17 transactions · 16 stateful · 2026-09-04 05:31:33 UTC

Parallelism

76/100

Blocked

56%

Avg conflicts / tx

0.76

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,817,940  ·  17 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

0x987859be…2686

0x34b655…2a6f

6 touches
3 conflicts

0x4dffc33e…068d

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0xd98afa6e…3364

0x34b655…2a6f

6 touches
3 conflicts

0x6324ccc9…14fd

0x34b655…2a6f

6 touches
3 conflicts

0x3d13406e…eff1

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x7daf6443…fd36

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 0x987859bea4…3e2686

← previous block·next block →recent activity