← previous blocknext block →recent activity

Analyzing

Block #73,387,752

18 transactions · 17 stateful · 2026-05-09 04:44:21 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,387,752  ·  18 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

0x1b9e654e…0a08

0x34b655…2a6f

6 touches
3 conflicts

0xd84e22f4…ccfb

0x34b655…2a6f

6 touches
3 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

6 touches
3 conflicts

0x908d4442…2c4b

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x703307bc…8fcf

0x34b655…2a6f

4 touches
1 conflict

0x9a7ae597…3816

0x34b655…2a6f

4 touches
1 conflict

0xa598353a…527d

0x34b655…2a6f

4 touches
1 conflict

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: 0x34b6552d…112a6f

3 conflicts on slot 0x1b9e654ec8…aa0a08

← previous block·next block →recent activity