← previous blocknext block →recent activity

Analyzing

Block #112,487,240

18 transactions · 18 stateful · 2026-10-11 14:02:04 UTC

Parallelism

56/100

Blocked

56%

Avg conflicts / tx

1.11

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #112,487,240  ·  18 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

0xb7b446d2…2006

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x90968e91…6b1c

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0040

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0055

0x1b6862…e19c

4 touches
1 conflict

0x4979282b…2935

0x1b6862…e19c

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

6 conflicts on slot 0xb7b446d20b…4f2006

← previous block·next block →recent activity