← previous blocknext block →recent activity

Analyzing

Block #102,231,895

20 transactions · 19 stateful · 2026-09-05 16:27:12 UTC

Parallelism

80/100

Blocked

32%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,231,895  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x4f3cc09a…2804

0x34b655…2a6f

4 touches
1 conflict

0x6c7c1a4b…5751

0x34b655…2a6f

4 touches
1 conflict

0x6e7eb884…4fab

0x34b655…2a6f

4 touches
1 conflict

0x7daf6443…fd36

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

0x34b655…2a6f

4 touches
1 conflict

0x9bff3222…a246

0x34b655…2a6f

4 touches
1 conflict

0x9c088939…ddd7

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity