← previous blocknext block →recent activity

Analyzing

Block #112,486,125

26 transactions · 24 stateful · 2026-10-11 13:56:27 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #112,486,125  ·  26 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

0xccebf5c5…8758

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x7e356592…de78

0xd32edf…ff58

7 touches
6 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

6 touches
3 conflicts

0x6235638c…643a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

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 0xccebf5c5cb…c88758

← previous block·next block →recent activity