← previous blocknext block →recent activity

Analyzing

Block #107,803,295

23 transactions · 19 stateful · 2026-09-25 04:56:49 UTC

Parallelism

78/100

Blocked

32%

Avg conflicts / tx

0.43

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,803,295  ·  23 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

0xbdd97c21…e3d0

0x34b655…2a6f

8 touches
6 conflicts

0xcf8b9b8e…93a3

0x34b655…2a6f

6 touches
3 conflicts

0xa38c430a…e3cb

0x34b655…2a6f

6 touches
3 conflicts

0x9ff4ca89…6115

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6674a6df…0368

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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

6 conflicts on slot 0xbdd97c213f…cee3d0

← previous block·next block →recent activity