← previous blocknext block →recent activity

Analyzing

Block #107,838,997

25 transactions · 23 stateful · 2026-09-25 07:56:29 UTC

Parallelism

68/100

Blocked

39%

Avg conflicts / tx

1.16

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #107,838,997  ·  25 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x25144f94…1854

0x34b655…2a6f

14 touches
21 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x8e669d78…3098

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x2328941c…84d3

0x34b655…2a6f

4 touches
1 conflict

0x3750b746…5a9e

0x34b655…2a6f

4 touches
1 conflict

0x3a7fb5b5…f0e5

0x34b655…2a6f

4 touches
1 conflict

0x790c39b8…c45a

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

21 conflicts on slot 0x25144f94f3…701854

← previous block·next block →recent activity