← previous blocknext block →recent activity

Analyzing

Block #107,812,755

26 transactions · 21 stateful · 2026-09-25 05:44:25 UTC

Parallelism

69/100

Blocked

43%

Avg conflicts / tx

0.96

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #107,812,755  ·  26 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xe1c4e5ce…0dec

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0xfd4e632c…e14c

0x34b655…2a6f

8 touches
6 conflicts

0x5ad5e6de…e7ad

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xaa654491…2ca4

0x34b655…2a6f

6 touches
3 conflicts

0xb64b9585…6270

0x34b655…2a6f

6 touches
3 conflicts

0xc32c7104…6608

0x34b655…2a6f

6 touches
3 conflicts

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 0xe1c4e5ce15…770dec

← previous block·next block →recent activity