← previous blocknext block →recent activity

Analyzing

Block #112,489,637

16 transactions · 14 stateful · 2026-10-11 14:14:07 UTC

Parallelism

75/100

Blocked

57%

Avg conflicts / tx

0.88

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #112,489,637  ·  16 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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xccebf5c5…8758

0x34b655…2a6f

6 touches
3 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

6 touches
3 conflicts

0xf96fd6ab…2f90

0x34b655…2a6f

6 touches
3 conflicts

0x53057a6c…ce62

0x34b655…2a6f

4 touches
1 conflict

0x5961f9aa…5fe2

0x34b655…2a6f

4 touches
1 conflict

0x5d80f962…1a26

0x34b655…2a6f

4 touches
1 conflict

0x621324da…9e79

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

3 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity