← previous blocknext block →recent activity

Analyzing

Block #112,473,450

23 transactions · 22 stateful · 2026-10-11 12:52:41 UTC

Parallelism

61/100

Blocked

45%

Avg conflicts / tx

1.35

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #112,473,450  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

10 touches
10 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x53fe4072…9147

0x34b655…2a6f

6 touches
3 conflicts

0x4fff38a1…75ff

0x34b655…2a6f

4 touches
1 conflict

0x8b501dcf…1040

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

10 conflicts on slot 0xccebf5c5cb…c88758

← previous block·next block →recent activity