← previous blocknext block →recent activity

Analyzing

Block #101,992,808

38 transactions · 17 stateful · 2026-09-04 20:15:30 UTC

Parallelism

92/100

Blocked

29%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #101,992,808  ·  38 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

0x045532dd…4b7d

0x34b655…2a6f

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0xeb1b66a1…ce4e

0x34b655…2a6f

4 touches
1 conflict

0xca544518…82c2

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x04d4f30d…4dfb

0x34b655…2a6f

4 touches
1 conflict

0x1dc71894…1884

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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 0x045532dd4b…244b7d

← previous block·next block →recent activity