← previous blocknext block →recent activity

Analyzing

Block #105,931,442

23 transactions · 20 stateful · 2026-09-18 15:51:51 UTC

Parallelism

87/100

Blocked

35%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #105,931,442  ·  23 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x3c9b10c1…d791

0x34b655…2a6f

4 touches
1 conflict

0x463e1e6b…87b5

0x34b655…2a6f

4 touches
1 conflict

0x55cde02d…89cb

0x34b655…2a6f

4 touches
1 conflict

0x5746581b…0cb1

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

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

3 conflicts on slot 0x51fc8795c8…57126f

← previous block·next block →recent activity