Block #73,202,074

← previous blocknext block →recent activity

Analyzing

Block #73,202,074

20 transactions · 13 stateful · 2026-05-08 08:09:11 UTC

Parallelism

75/100

Blocked

38%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,202,074  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd1c2075e…5658

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x62af37f3…02f2

0x065c9d…c394

2 touches
0 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

2 touches
0 conflicts

0x70b2f813…783c

0x2a68ba…90c5

2 touches
0 conflicts

0x264c6e4e…cbb6

0x3bd359…433a

2 touches
0 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

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

10 conflicts on slot 0xd1c2075eee…175658

← previous block·next block →recent activity