← previous blocknext block →recent activity

Analyzing

Block #73,263,119

20 transactions · 15 stateful · 2026-05-08 14:55:06 UTC

Parallelism

80/100

Blocked

27%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,263,119  ·  20 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

0x41096a66…531c

0xd32edf…ff58

7 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x565a9842…77fe

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 conflicts

0x8d0dfe2c…3345

0x2a68ba…90c5

2 touches
0 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

2 touches
0 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: 0xd32edf66…9fff58

6 conflicts on slot 0x41096a661b…ce531c

← previous block·next block →recent activity