← previous blocknext block →recent activity

Analyzing

Block #107,839,460

28 transactions · 26 stateful · 2026-09-25 07:58:49 UTC

Parallelism

71/100

Blocked

46%

Avg conflicts / tx

1.11

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #107,839,460  ·  28 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

0xb195cffa…8098

0x34b655…2a6f

14 touches
21 conflicts

0x8cac1429…a7e9

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0xbeedaa05…9eda

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0xaa6eea57…276d

0x34b655…2a6f

6 touches
3 conflicts

0x88e771e8…7d4a

0x34b655…2a6f

4 touches
1 conflict

0xa69bb4e1…f2bb

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 0xb195cffa54…368098

← previous block·next block →recent activity