← previous blocknext block →recent activity

Analyzing

Block #101,991,094

18 transactions · 18 stateful · 2026-09-04 20:06:50 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,991,094  ·  18 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

0x22f10271…841d

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x29a58269…011a

0x34b655…2a6f

4 touches
1 conflict

0x51f32324…de5c

0x34b655…2a6f

4 touches
1 conflict

0x5dcccdd2…3e80

0x34b655…2a6f

4 touches
1 conflict

0x7daf6443…fd36

0x34b655…2a6f

4 touches
1 conflict

0x8849e72f…b522

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

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 0x22f10271ce…96841d

← previous block·next block →recent activity