← previous blocknext block →recent activity

Analyzing

Block #106,957,240

16 transactions · 16 stateful · 2026-09-22 05:55:51 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,957,240  ·  16 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

0x0463db49…5d05

0x34b655…2a6f

6 touches
3 conflicts

0x155e52ca…fac7

0x34b655…2a6f

6 touches
3 conflicts

0x2d34e814…4baa

0x851145…3f07

4 touches
1 conflict

0x8edc11b2…8a6f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xccebf5c5…8758

0x34b655…2a6f

4 touches
1 conflict

0xe7e580a2…39ed

0x34b655…2a6f

4 touches
1 conflict

0xfcef6587…476d

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 0x0463db492b…795d05

← previous block·next block →recent activity