← previous blocknext block →recent activity

Analyzing

Block #73,170,742

12 transactions · 10 stateful · 2026-05-08 04:40:21 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,170,742  ·  12 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

0xd0e2cff8…7c29

0xd32edf…ff58

7 touches
6 conflicts

0x8e66da19…66b6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8dbbd426…2f41

0x065c9d…c394

2 touches
0 conflicts

0xbd0e1425…7ec7

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

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 0xd0e2cff8c6…9d7c29

← previous block·next block →recent activity