← previous blocknext block →recent activity

Analyzing

Block #106,187,316

24 transactions · 21 stateful · 2026-09-19 13:19:45 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.54

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,187,316  ·  24 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xd17580f9…ece1

0x754704…b603

4 touches
1 conflict

0xedc6be2b…c135

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0xfefb0189…f726

0x34b655…2a6f

4 touches
1 conflict

0x1b25f260…c429

0x34b655…2a6f

4 touches
1 conflict

0x2d071de0…c86e

0x34b655…2a6f

4 touches
1 conflict

0x4156ee24…e00d

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity