← previous blocknext block →recent activity

Analyzing

Block #107,642,889

18 transactions · 16 stateful · 2026-09-24 15:28:01 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #107,642,889  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf8b7e65f…2816

0x34b655…2a6f

4 touches
1 conflict

0xf3db9111…8b2b

0x34b655…2a6f

4 touches
1 conflict

0xf33c3f68…d6b2

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x00e21a9f…3583

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

1 conflict on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity