← previous blocknext block →recent activity

Analyzing

Block #73,478,148

9 transactions · 9 stateful · 2026-05-09 14:45:56 UTC

Parallelism

67/100

Blocked

22%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,478,148  ·  9 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

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xa46bb8c3…fb48

0x065c9d…c394

3 touches
1 conflict

0x6743ceee…448e

0xd32edf…ff58

3 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0xa507818b…d6f3

0x065c9d…c394

2 touches
0 conflicts

0xd84d1890…cd9e

0x065c9d…c394

2 touches
0 conflicts

0xf537eaa0…73c8

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

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

1 conflict on slot 0xc9e9752290…9c3519

← previous block·next block →recent activity