← previous blocknext block →recent activity

Analyzing

Block #106,934,895

27 transactions · 24 stateful · 2026-09-22 04:03:22 UTC

Parallelism

78/100

Blocked

29%

Avg conflicts / tx

0.63

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,934,895  ·  27 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

0x6758e5b6…93ae

0x34b655…2a6f

12 touches
15 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

12 touches
15 conflicts

0x8d5fc820…1750

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x2021fb2a…d63b

0x34b655…2a6f

4 touches
1 conflict

0x2021fb2a…d63c

0x34b655…2a6f

4 touches
1 conflict

0x2592d715…a50e

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

15 conflicts on slot 0x6758e5b62b…1393ae

← previous block·next block →recent activity