← previous blocknext block →recent activity

Analyzing

Block #106,473,601

21 transactions · 20 stateful · 2026-09-20 13:20:39 UTC

Parallelism

52/100

Blocked

50%

Avg conflicts / tx

2.19

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,473,601  ·  21 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xfb111bae…5303

0x34b655…2a6f

20 touches
45 conflicts

0xcd9ba26b…108d

0x34b655…2a6f

18 touches
36 conflicts

0x23592ab4…9ba8

0x34b655…2a6f

10 touches
10 conflicts

0x92b49f44…ee4f

0x34b655…2a6f

8 touches
6 conflicts

0x172b0de5…980b

0x34b655…2a6f

8 touches
6 conflicts

0xe22ab637…7a8e

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x781266b2…e87c

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

45 conflicts on slot 0xfb111bae3a…475303

← previous block·next block →recent activity