← previous blocknext block →recent activity

Analyzing

Block #73,187,877

8 transactions · 7 stateful · 2026-05-08 06:34:41 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,187,877  ·  8 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xba576bc0…56dd

0x34b655…2a6f

4 touches
1 conflict

0xc1f28224…cb43

0x34b655…2a6f

4 touches
1 conflict

0x8e66da19…66b6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x2a354a63…0515

0x065c9d…c394

2 touches
0 conflicts

0x61024ff2…bb06

0x065c9d…c394

2 touches
0 conflicts

0x7420b8f1…e0eb

0x065c9d…c394

2 touches
0 conflicts

0xca7422e0…dda3

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

1 conflict on slot 0xba576bc006…6c56dd

← previous block·next block →recent activity