← previous blocknext block →recent activity

Analyzing

Block #112,490,510

20 transactions · 19 stateful · 2026-10-11 14:18:31 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.95

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #112,490,510  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x7be97c83…148f

0x34b655…2a6f

8 touches
6 conflicts

0xccebf5c5…8758

0x34b655…2a6f

8 touches
6 conflicts

0xdad20621…06b1

0x34b655…2a6f

8 touches
6 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0055

0x1b6862…e19c

4 touches
1 conflict

0x15427cff…e8f8

0x1b6862…e19c

4 touches
1 conflict

0xd59f6ed1…03e8

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 0x7be97c83f9…bc148f

← previous block·next block →recent activity