← previous blocknext block →recent activity

Analyzing

Block #107,651,618

20 transactions · 19 stateful · 2026-09-24 16:12:02 UTC

Parallelism

85/100

Blocked

26%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #107,651,618  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xcc844ab5…4c6d

0x34b655…2a6f

6 touches
3 conflicts

0xd31f440a…c5a8

0x34b655…2a6f

6 touches
3 conflicts

0x1393df1d…afbd

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35d

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x42522e76…2592

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x7462b8f2…6312

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

3 conflicts on slot 0xcc844ab542…814c6d

← previous block·next block →recent activity