← previous blocknext block →recent activity

Analyzing

Block #112,526,062

21 transactions · 18 stateful · 2026-10-11 17:17:24 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

1.24

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #112,526,062  ·  21 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

0xccebf5c5…8758

0x34b655…2a6f

12 touches
15 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

8 touches
6 conflicts

0xd5cad11b…c1a5

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x464a82ff…41de

0x34b655…2a6f

6 touches
3 conflicts

0x607973ca…5de5

0x34b655…2a6f

4 touches
1 conflict

0x61074ef0…9b6f

0x34b655…2a6f

4 touches
1 conflict

0x6d105005…3cc9

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

15 conflicts on slot 0xccebf5c5cb…c88758

← previous block·next block →recent activity