← previous blocknext block →recent activity

Analyzing

Block #106,921,940

23 transactions · 23 stateful · 2026-09-22 02:58:10 UTC

Parallelism

61/100

Blocked

48%

Avg conflicts / tx

1.17

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #106,921,940  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x8590b692…b267

0x34b655…2a6f

12 touches
15 conflicts

0x7ca519d1…4f93

0x34b655…2a6f

10 touches
10 conflicts

0xccebf5c5…8758

0x34b655…2a6f

10 touches
10 conflicts

0x469dac8d…3411

0x34b655…2a6f

10 touches
10 conflicts

0x34eb3605…9253

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

15 conflicts on slot 0x8590b69238…6ab267

← previous block·next block →recent activity