← previous blocknext block →recent activity

Analyzing

Block #73,670,537

8 transactions · 8 stateful · 2026-05-10 12:09:38 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

0.88

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,670,537  ·  8 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

0x529acb6a…fcc6

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0xa4259373…e88e

0x065c9d…c394

3 touches
1 conflict

0x6b65eae3…6fc6

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0xafd5d233…849b

0x065c9d…c394

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: 0x065c9d28…a9c394

6 conflicts on slot 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity