← previous blocknext block →recent activity

Analyzing

Block #105,855,681

18 transactions · 17 stateful · 2026-09-18 09:29:40 UTC

Parallelism

72/100

Blocked

47%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #105,855,681  ·  18 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

0x9c83a7b1…e305

0x34b655…2a6f

10 touches
10 conflicts

0xd17580f9…ece1

0x754704…b603

8 touches
6 conflicts

0x6262c3fa…bb1d

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x18978822…2623

0x34b655…2a6f

4 touches
1 conflict

0x31e45f46…ad22

0x34b655…2a6f

4 touches
1 conflict

0x65bdc5fa…d7f3

0x34b655…2a6f

4 touches
1 conflict

0x931975c2…b7b3

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

10 conflicts on slot 0x9c83a7b19e…36e305

← previous block·next block →recent activity