← previous blocknext block →recent activity

Analyzing

Block #105,850,939

18 transactions · 18 stateful · 2026-09-18 09:05:47 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.11

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #105,850,939  ·  18 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

0x6ceb0938…d5b7

0x34b655…2a6f

12 touches
15 conflicts

0x1d9867ad…6d9a

0x34b655…2a6f

8 touches
6 conflicts

0x89999c15…fdac

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x4abfb389…18f4

0x34b655…2a6f

6 touches
3 conflicts

0xf788c790…e66f

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x4d4389b2…6e07

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 0x6ceb093846…37d5b7

← previous block·next block →recent activity