Block #73,202,049

← previous blocknext block →recent activity

Analyzing

Block #73,202,049

22 transactions · 14 stateful · 2026-05-08 08:09:01 UTC

Parallelism

73/100

Blocked

50%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,202,049  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x36be7108…d32a

0xd32edf…ff58

11 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x3dd0a783…4d66

0x065c9d…c394

4 touches
1 conflict

0x48db5ced…ab2f

0x065c9d…c394

4 touches
1 conflict

0xce7bfe5e…5e58

0x065c9d…c394

4 touches
1 conflict

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xec2e5d55…e069

0x065c9d…c394

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: 0xd32edf66…9fff58

15 conflicts on slot 0x36be7108b4…07d32a

← previous block·next block →recent activity