← previous blocknext block →recent activity

Analyzing

Block #107,816,039

18 transactions · 17 stateful · 2026-09-25 06:00:57 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #107,816,039  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc7679110…572d

0x34b655…2a6f

10 touches
10 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x0b3f5b25…7d77

0x34b655…2a6f

4 touches
1 conflict

0x2328941c…84d3

0x34b655…2a6f

4 touches
1 conflict

0x3ea25e92…a36d

0x34b655…2a6f

4 touches
1 conflict

0x4d1400eb…c023

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

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

10 conflicts on slot 0xc7679110cf…22572d

← previous block·next block →recent activity