← previous blocknext block →recent activity

Analyzing

Block #73,490,593

18 transactions · 13 stateful · 2026-05-09 16:08:50 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,490,593  ·  18 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

0xfe3bddd2…8b48

0x3bd359…433a

8 touches
6 conflicts

0xbc003209…2c48

0xd32edf…ff58

5 touches
3 conflicts

0xd06cc746…27e4

0x350035…7777

4 touches
1 conflict

0x00000000…0005

0x1397bd…f779

2 touches
0 conflicts

0x67d47cb1…3fa0

0x188d58…ea8e

2 touches
0 conflicts

0x67d47cb1…3fa2

0x188d58…ea8e

2 touches
0 conflicts

0xbc467e7a…af36

0x21e325…7777

2 touches
0 conflicts

0xd06cc746…27e4

0x21e325…7777

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: 0x3bd359c1…15433a

6 conflicts on slot 0xfe3bddd26f…bb8b48

← previous block·next block →recent activity