← previous blocknext block →recent activity

Analyzing

Block #112,610,393

22 transactions · 21 stateful · 2026-10-12 00:21:41 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #112,610,393  ·  22 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

0xccebf5c5…8758

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xd4ea15b9…58bf

0x34b655…2a6f

6 touches
3 conflicts

0x2d3930d3…c9b8

0x34b655…2a6f

4 touches
1 conflict

0x3e09ea78…2d8b

0x34b655…2a6f

4 touches
1 conflict

0x5ffe5c25…8992

0x34b655…2a6f

4 touches
1 conflict

0x0f8c87bf…3d31

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