← previous blocknext block →recent activity

Analyzing

Block #112,478,795

20 transactions · 18 stateful · 2026-10-11 13:19:34 UTC

Parallelism

65/100

Blocked

56%

Avg conflicts / tx

1.1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #112,478,795  ·  20 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

0xe720a4c6…8eb0

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x733c7779…a647

0x34b655…2a6f

6 touches
3 conflicts

0xdad20621…06b1

0x34b655…2a6f

4 touches
1 conflict

0x107b89e4…470d

0x34b655…2a6f

4 touches
1 conflict

0x36890fff…f3d1

0x34b655…2a6f

4 touches
1 conflict

0x68c28140…2e29

0x34b655…2a6f

4 touches
1 conflict

0x6f6fc26c…3e34

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 0xe720a4c698…508eb0

← previous block·next block →recent activity