← previous blocknext block →recent activity

Analyzing

Block #104,696,217

17 transactions · 17 stateful · 2026-09-14 08:09:58 UTC

Parallelism

65/100

Blocked

41%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #104,696,217  ·  17 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

0x25821874…068f

0x34b655…2a6f

6 touches
3 conflicts

0x72083f0d…082a

0x34b655…2a6f

6 touches
3 conflicts

0x9ecfa3dd…0d69

0x34b655…2a6f

6 touches
3 conflicts

0xb240b520…a88a

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x48b13e5e…3c2a

0x34b655…2a6f

4 touches
1 conflict

0x4d4389b2…6e07

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

3 conflicts on slot 0x258218741f…b9068f

← previous block·next block →recent activity