← previous blocknext block →recent activity

Analyzing

Block #106,388,616

21 transactions · 18 stateful · 2026-09-20 06:12:53 UTC

Parallelism

81/100

Blocked

39%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,388,616  ·  21 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

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x4681609f…6493

0x34b655…2a6f

8 touches
6 conflicts

0x49cbdb1b…bda4

0x065c9d…c394

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x16fb6f47…bbdf

0x34b655…2a6f

4 touches
1 conflict

0x3643741b…109c

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 0xea02471df2…601542

← previous block·next block →recent activity