← previous blocknext block →recent activity

Analyzing

Block #105,760,766

19 transactions · 18 stateful · 2026-09-18 01:30:31 UTC

Parallelism

63/100

Blocked

44%

Avg conflicts / tx

1.47

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #105,760,766  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xeb5b61a2…b2bc

0x34b655…2a6f

12 touches
15 conflicts

0x31e0d360…e742

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0x43e3decb…be40

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x89999c15…fdac

0x34b655…2a6f

8 touches
6 conflicts

0x9ff4ca89…6115

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

15 conflicts on slot 0xeb5b61a29c…4fb2bc

← previous block·next block →recent activity