← previous blocknext block →recent activity

Analyzing

Block #105,920,413

20 transactions · 19 stateful · 2026-09-18 14:56:19 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

0.6

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #105,920,413  ·  20 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

0x4089d428…b018

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0xe7cc46a3…3165

0x34b655…2a6f

6 touches
3 conflicts

0xf5d99264…de4e

0x34b655…2a6f

6 touches
3 conflicts

0x3b6e959d…158f

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xce1d43c8…d042

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 0x4089d42830…afb018

← previous block·next block →recent activity