← previous blocknext block →recent activity

Analyzing

Block #108,677,522

19 transactions · 18 stateful · 2026-09-28 06:17:16 UTC

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

0.84

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #108,677,522  ·  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

0x640feb0e…e1b7

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x318f9d69…8130

0x34b655…2a6f

6 touches
3 conflicts

0x06dde6ae…1ffe

0x34b655…2a6f

6 touches
3 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

4 touches
1 conflict

0x8e5616e0…ab21

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 0x640feb0e76…a9e1b7

← previous block·next block →recent activity