← previous blocknext block →recent activity

Analyzing

Block #73,348,374

14 transactions · 13 stateful · 2026-05-09 00:22:25 UTC

Parallelism

71/100

Blocked

31%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,348,374  ·  14 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

0x8130ea69…f67f

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xea605e6b…3422

0x065c9d…c394

4 touches
1 conflict

0x52b4b0fe…aede

0x065c9d…c394

3 touches
1 conflict

0x8971b008…395b

0x065c9d…c394

3 touches
1 conflict

0x4dd1db39…a994

0x188d58…ea8e

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x00000000…0004

0x1e240e…10d4

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 0x8130ea6976…25f67f

← previous block·next block →recent activity