Block #73,176,347

← previous blocknext block →recent activity

Analyzing

Block #73,176,347

12 transactions · 12 stateful · 2026-05-08 05:17:47 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,176,347  ·  12 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x2a354a63…0515

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x6a3c47e0…abf0

0x065c9d…c394

2 touches
0 conflicts

0x7f189cf6…afab

0x065c9d…c394

2 touches
0 conflicts

0x8a140cd8…9b35

0x065c9d…c394

2 touches
0 conflicts

0x8e66da19…66b6

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity