← previous blocknext block →recent activity

Analyzing

Block #107,813,377

27 transactions · 22 stateful · 2026-09-25 05:47:33 UTC

Parallelism

81/100

Blocked

32%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,813,377  ·  27 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xa23b9051…392f

0x34b655…2a6f

10 touches
10 conflicts

0x2d0d6e63…0ffc

0x34b655…2a6f

6 touches
3 conflicts

0xbb96f8af…205f

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0xaae6463e…bfcc

0x34b655…2a6f

4 touches
1 conflict

0x340c945c…288a

0x34b655…2a6f

4 touches
1 conflict

0x42522e76…2592

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

10 conflicts on slot 0xa23b905120…88392f

← previous block·next block →recent activity