← previous blocknext block →recent activity

Analyzing

Block #108,960,313

20 transactions · 20 stateful · 2026-09-29 06:04:44 UTC

Parallelism

70/100

Blocked

40%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #108,960,313  ·  20 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

0x4b36c7dd…da26

0x34b655…2a6f

10 touches
10 conflicts

0xe9ecfc90…8891

0x34b655…2a6f

8 touches
6 conflicts

0x900e0d7a…6f85

0x34b655…2a6f

6 touches
3 conflicts

0xd4230a60…bd13

0x34b655…2a6f

6 touches
3 conflicts

0xf2515e91…2f12

0x34b655…2a6f

6 touches
3 conflicts

0xbefdde57…cd0e

0x34b655…2a6f

6 touches
3 conflicts

0xc4c059d8…185d

0x34b655…2a6f

6 touches
3 conflicts

0x5655f5c3…6b75

0x34b655…2a6f

6 touches
3 conflicts

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 0x4b36c7ddcb…66da26

← previous block·next block →recent activity