← previous blocknext block →recent activity

Analyzing

Block #104,868,744

20 transactions · 19 stateful · 2026-09-14 22:40:58 UTC

Parallelism

70/100

Blocked

32%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #104,868,744  ·  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

0x62023181…811e

0x34b655…2a6f

6 touches
3 conflicts

0xfa09be5a…1e79

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x54c6fb44…369a

0x34b655…2a6f

4 touches
1 conflict

0x95b1af0a…41ea

0x34b655…2a6f

4 touches
1 conflict

0xa7013be2…c0a8

0x34b655…2a6f

4 touches
1 conflict

0xc09c3422…3c8b

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 0x6202318167…4d811e

← previous block·next block →recent activity