← previous blocknext block →recent activity

Analyzing

Block #112,585,420

23 transactions · 20 stateful · 2026-10-11 22:16:03 UTC

Parallelism

83/100

Blocked

30%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #112,585,420  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x125f12…a50b

4 touches
1 conflict

0x2ef4207d…4f4b

0x34b655…2a6f

4 touches
1 conflict

0xccebf5c5…8758

0x34b655…2a6f

4 touches
1 conflict

0xdc8d4ee0…def3

0x34b655…2a6f

4 touches
1 conflict

0x6cd6078c…7e9b

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 0xbde524f475…b143bf

← previous block·next block →recent activity