← previous blocknext block →recent activity

Analyzing

Block #112,490,962

22 transactions · 20 stateful · 2026-10-11 14:20:47 UTC

Parallelism

68/100

Blocked

45%

Avg conflicts / tx

0.91

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #112,490,962  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x62aca140…f539

0x34b655…2a6f

8 touches
6 conflicts

0x51af0e92…4020

0x34b655…2a6f

8 touches
6 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0040

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0055

0x1b6862…e19c

4 touches
1 conflict

0x106f80f5…d418

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

← previous block·next block →recent activity