← previous blocknext block →recent activity

Analyzing

Block #101,937,685

19 transactions · 19 stateful · 2026-09-04 15:35:54 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #101,937,685  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xfd713bab…a651

0x34b655…2a6f

6 touches
3 conflicts

0x891562b1…8216

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x93aaefce…5be5

0x34b655…2a6f

6 touches
3 conflicts

0x987859be…2686

0x34b655…2a6f

6 touches
3 conflicts

0xb47d4bdd…6172

0x34b655…2a6f

6 touches
3 conflicts

0xc52785b9…08f8

0x34b655…2a6f

6 touches
3 conflicts

0xd02ebff8…fe31

0x34b655…2a6f

6 touches
3 conflicts

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 0xfd713bab1a…98a651

← previous block·next block →recent activity