← previous blocknext block →recent activity

Analyzing

Block #112,611,873

24 transactions · 20 stateful · 2026-10-12 00:29:08 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #112,611,873  ·  24 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

0xf98f0ade…20c2

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x6d5d1fb5…86a7

0x34b655…2a6f

6 touches
3 conflicts

0x7d9ef283…ddd1

0x34b655…2a6f

6 touches
3 conflicts

0x83646eb5…5a21

0x34b655…2a6f

4 touches
1 conflict

0xa7d3cb90…e1d9

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

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 0xf98f0ade36…2420c2

← previous block·next block →recent activity