← previous blocknext block →recent activity

Analyzing

Block #112,235,632

17 transactions · 15 stateful · 2026-10-10 16:56:11 UTC

Parallelism

65/100

Blocked

67%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #112,235,632  ·  17 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

0x46058954…b868

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x336486a4…20bd

0x34b655…2a6f

6 touches
3 conflicts

0x36a76bd2…1fb0

0x34b655…2a6f

4 touches
1 conflict

0x3a5cd535…3546

0x34b655…2a6f

4 touches
1 conflict

0x5a65207b…4f30

0x34b655…2a6f

4 touches
1 conflict

0x5b37bb6b…aaff

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 0x46058954bb…49b868

← previous block·next block →recent activity