← previous blocknext block →recent activity

Analyzing

Block #106,109,645

19 transactions · 18 stateful · 2026-09-19 06:48:51 UTC

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

1.05

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,109,645  ·  19 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

0x159cff26…7665

0x34b655…2a6f

8 touches
6 conflicts

0x63fba213…5ce2

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x46483cb1…e7ca

0x34b655…2a6f

8 touches
6 conflicts

0xf91d37c7…39f1

0x34b655…2a6f

6 touches
3 conflicts

0x3aca64ec…7cbb

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x4acd9e51…2863

0x34b655…2a6f

6 touches
3 conflicts

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 0x159cff262c…e57665

← previous block·next block →recent activity