← previous blocknext block →recent activity

Analyzing

Block #112,491,791

27 transactions · 22 stateful · 2026-10-11 14:24:58 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #112,491,791  ·  27 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

0x1b5989b4…4dbf

0x34b655…2a6f

6 touches
3 conflicts

0xccebf5c5…8758

0x34b655…2a6f

6 touches
3 conflicts

0x3d675524…b454

0x34b655…2a6f

6 touches
3 conflicts

0x57e5abc1…286f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xb4656137…5858

0x34b655…2a6f

4 touches
1 conflict

0xc0515e26…c53e

0x34b655…2a6f

4 touches
1 conflict

0xc57e111c…f789

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 0x1b5989b404…ca4dbf

← previous block·next block →recent activity