← previous blocknext block →recent activity

Analyzing

Block #105,856,826

33 transactions · 30 stateful · 2026-09-18 09:35:25 UTC

Parallelism

82/100

Blocked

23%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #105,856,826  ·  33 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

0xb194d30c…6af3

0x34b655…2a6f

12 touches
15 conflicts

0x97e4c862…4419

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x203d3e2c…fa40

0x34b655…2a6f

8 touches
6 conflicts

0x9ff4ca89…6115

0x34b655…2a6f

8 touches
6 conflicts

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0x92b49f44…ee4f

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

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 0xb194d30c47…4d6af3

← previous block·next block →recent activity