← previous blocknext block →recent activity

Analyzing

Block #109,177,461

19 transactions · 17 stateful · 2026-09-30 00:20:34 UTC

Parallelism

74/100

Blocked

41%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #109,177,461  ·  19 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

0xf6deafb5…5c25

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x9eef1610…1564

0x34b655…2a6f

6 touches
3 conflicts

0x23769ebc…c8ed

0x34b655…2a6f

4 touches
1 conflict

0x6636a104…d595

0x34b655…2a6f

4 touches
1 conflict

0x9ff94a68…7ae8

0x34b655…2a6f

4 touches
1 conflict

0xab7f4e6b…8093

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 0xf6deafb553…9e5c25

← previous block·next block →recent activity