← previous blocknext block →recent activity

Analyzing

Block #112,484,797

22 transactions · 21 stateful · 2026-10-11 13:49:46 UTC

Parallelism

68/100

Blocked

48%

Avg conflicts / tx

1.36

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #112,484,797  ·  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

10 touches
10 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

10 touches
10 conflicts

0x931975c2…b7b3

0x34b655…2a6f

8 touches
6 conflicts

0x8f2e60c1…a529

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xdad20621…06b1

0x34b655…2a6f

6 touches
3 conflicts

0x44de3f73…1146

0x34b655…2a6f

4 touches
1 conflict

0x6ac4a9ce…5f63

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