← previous blocknext block →recent activity

Analyzing

Block #112,484,784

21 transactions · 19 stateful · 2026-10-11 13:49:42 UTC

Parallelism

62/100

Blocked

47%

Avg conflicts / tx

1.14

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #112,484,784  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x11f1df32…c819

0x34b655…2a6f

10 touches
10 conflicts

0xccebf5c5…8758

0x34b655…2a6f

8 touches
6 conflicts

0x931975c2…b7b3

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6426

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x53057a6c…ce62

0x34b655…2a6f

6 touches
3 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

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

10 conflicts on slot 0x11f1df3252…a1c819

← previous block·next block →recent activity