← previous blocknext block →recent activity

Analyzing

Block #101,925,681

18 transactions · 17 stateful · 2026-09-04 14:34:55 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,925,681  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x33761f7c…8f85

0x34b655…2a6f

10 touches
10 conflicts

0xca796e05…846f

0x34b655…2a6f

8 touches
6 conflicts

0x3fb3f2e2…fef3

0x34b655…2a6f

6 touches
3 conflicts

0xe0da07e4…ccf2

0x34b655…2a6f

6 touches
3 conflicts

0x2f17174f…68b4

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xda50c9d5…674e

0x34b655…2a6f

6 touches
3 conflicts

0xdec2aeb2…0586

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

10 conflicts on slot 0x33761f7c9a…148f85

← previous block·next block →recent activity