← previous blocknext block →recent activity

Analyzing

Block #101,838,069

15 transactions · 15 stateful · 2026-09-04 07:12:48 UTC

Parallelism

53/100

Blocked

67%

Avg conflicts / tx

1.13

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #101,838,069  ·  15 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x451e482b…7e7d

0x34b655…2a6f

6 touches
3 conflicts

0x23bdd522…c347

0x34b655…2a6f

4 touches
1 conflict

0x3e3f27ce…580c

0x34b655…2a6f

4 touches
1 conflict

0x4188cc5f…2d2e

0x34b655…2a6f

4 touches
1 conflict

0x46c14e01…ff09

0x34b655…2a6f

4 touches
1 conflict

0x49299fcf…c552

0x34b655…2a6f

4 touches
1 conflict

0x4d5053d1…3b7d

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 0xca841faae5…71486a

← previous block·next block →recent activity