← previous blocknext block →recent activity

Analyzing

Block #112,528,439

24 transactions · 23 stateful · 2026-10-11 17:29:21 UTC

Parallelism

75/100

Blocked

35%

Avg conflicts / tx

0.63

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #112,528,439  ·  24 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

0x46c14e01…ff09

0x34b655…2a6f

6 touches
3 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

6 touches
3 conflicts

0xccebf5c5…8758

0x34b655…2a6f

6 touches
3 conflicts

0x1b4fc04c…7352

0x34b655…2a6f

6 touches
3 conflicts

0x286711a5…b3bf

0x34b655…2a6f

4 touches
1 conflict

0x3093e806…bde2

0x34b655…2a6f

4 touches
1 conflict

0x40ab8032…3028

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

3 conflicts on slot 0x46c14e01c8…d5ff09

← previous block·next block →recent activity