← previous blocknext block →recent activity

Analyzing

Block #101,680,977

20 transactions · 17 stateful · 2026-09-03 18:02:41 UTC

Parallelism

80/100

Blocked

47%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,680,977  ·  20 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

0xf7772b49…fc12

0x34b655…2a6f

6 touches
3 conflicts

0x4f3cc09a…2804

0x34b655…2a6f

6 touches
3 conflicts

0x51af0e92…4020

0x34b655…2a6f

6 touches
3 conflicts

0x6823c28e…594c

0x34b655…2a6f

6 touches
3 conflicts

0x6c7c1a4b…5751

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0xa62eb46f…89b1

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

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 0xf7772b4910…d2fc12

← previous block·next block →recent activity