← previous blocknext block →recent activity

Analyzing

Block #106,367,417

18 transactions · 18 stateful · 2026-09-20 04:26:12 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,367,417  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x0463db49…5d05

0x34b655…2a6f

4 touches
1 conflict

0x1b25f260…c429

0x34b655…2a6f

4 touches
1 conflict

0x2130a548…c1de

0x34b655…2a6f

4 touches
1 conflict

0x31e47e6c…87f9

0x34b655…2a6f

4 touches
1 conflict

0x364036f4…10de

0x34b655…2a6f

4 touches
1 conflict

0x4681609f…6493

0x34b655…2a6f

4 touches
1 conflict

0x49b9fdd5…9c16

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity