← previous blocknext block →recent activity

Analyzing

Block #112,384,896

23 transactions · 16 stateful · 2026-10-11 05:27:08 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #112,384,896  ·  23 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

0x7bd229ad…63b2

0x34b655…2a6f

8 touches
6 conflicts

0xf5dc501b…831c

0x34b655…2a6f

8 touches
6 conflicts

0xccebf5c5…8758

0x34b655…2a6f

6 touches
3 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

6 touches
3 conflicts

0x8c211514…b757

0x34b655…2a6f

4 touches
1 conflict

0xb4656137…5858

0x34b655…2a6f

4 touches
1 conflict

0x19eceb21…04b4

0x34b655…2a6f

4 touches
1 conflict

0x2c8b3946…39d7

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 0x7bd229ade5…6b63b2

← previous block·next block →recent activity