← previous blocknext block →recent activity

Analyzing

Block #104,198,299

22 transactions · 20 stateful · 2026-09-12 14:02:49 UTC

Parallelism

82/100

Blocked

30%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #104,198,299  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x464a82ff…41de

0x34b655…2a6f

6 touches
3 conflicts

0x52e69143…95ad

0x065c9d…c394

4 touches
1 conflict

0xce827910…ff22

0x065c9d…c394

4 touches
1 conflict

0x1a2055c7…9054

0x34b655…2a6f

4 touches
1 conflict

0x640c4fb2…044a

0x34b655…2a6f

4 touches
1 conflict

0x7b41d5cd…00e6

0x34b655…2a6f

4 touches
1 conflict

0x8794596c…1dd4

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity