← previous blocknext block →recent activity

Analyzing

Block #101,661,812

26 transactions · 20 stateful · 2026-09-03 16:26:16 UTC

Parallelism

77/100

Blocked

45%

Avg conflicts / tx

0.69

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,661,812  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x17d87f0d…bfc5

0x34b655…2a6f

6 touches
3 conflicts

0x359866c7…de7b

0x34b655…2a6f

6 touches
3 conflicts

0xdd18ee05…d486

0x34b655…2a6f

6 touches
3 conflicts

0xbd22d0fc…64fd

0x34b655…2a6f

6 touches
3 conflicts

0x784d7a94…949f

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x08cf2849…1d89

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