← previous blocknext block →recent activity

Analyzing

Block #107,979,138

19 transactions · 18 stateful · 2026-09-25 19:41:59 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #107,979,138  ·  19 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

0x46483cb1…e7ca

0x34b655…2a6f

8 touches
6 conflicts

0xcc844ab5…4c6d

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x4996be87…663a

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0xba5743c7…21c1

0x1b6862…e19c

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x14b80268…69ef

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

6 conflicts on slot 0x46483cb14f…c1e7ca

← previous block·next block →recent activity