← previous blocknext block →recent activity

Analyzing

Block #112,084,527

21 transactions · 21 stateful · 2026-10-10 04:15:59 UTC

Parallelism

71/100

Blocked

43%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #112,084,527  ·  21 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

0x766f19bb…75dd

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x479ce48c…fa17

0x1b6862…e19c

6 touches
3 conflicts

0x132e96ad…6717

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x5eb428fc…b5e3

0xd32edf…ff58

5 touches
3 conflicts

0x3b3f053b…d6e1

0x34b655…2a6f

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 0x766f19bbd6…c975dd

← previous block·next block →recent activity