← previous blocknext block →recent activity

Analyzing

Block #73,643,104

16 transactions · 11 stateful · 2026-05-10 09:04:44 UTC

Parallelism

81/100

Blocked

27%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,643,104  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0xc46c1312…2605

0xd32edf…ff58

3 touches
1 conflict

0x334b8107…8f73

0x34b655…2a6f

2 touches
0 conflicts

0x3ca00e15…9c15

0x34b655…2a6f

2 touches
0 conflicts

0x4089d428…b018

0x34b655…2a6f

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity