← previous blocknext block →recent activity

Analyzing

Block #73,436,073

17 transactions · 13 stateful · 2026-05-09 10:05:53 UTC

Parallelism

76/100

Blocked

31%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,436,073  ·  17 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

0x0d0b2509…074d

0x3bd359…433a

8 touches
6 conflicts

0xe6455d1f…1029

0x754704…b603

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xb7e80483…5967

0xd32edf…ff58

3 touches
1 conflict

0x255b8112…44c0

0x065c9d…c394

2 touches
0 conflicts

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0xaae4c13e…8e38

0x065c9d…c394

2 touches
0 conflicts

0xf537eaa0…73c8

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

6 conflicts on slot 0x0d0b2509ae…4b074d

← previous block·next block →recent activity