← previous blocknext block →recent activity

Analyzing

Block #73,336,302

16 transactions · 13 stateful · 2026-05-08 23:02:05 UTC

Parallelism

69/100

Blocked

31%

Avg conflicts / tx

0.69

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,336,302  ·  16 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

0x4f57c17a…2b07

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb85

0x1b6862…e19c

4 touches
1 conflict

0x7b21bda3…cebf

0x065c9d…c394

2 touches
0 conflicts

0x8fd411a4…0267

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

10 conflicts on slot 0x4f57c17afe…942b07

← previous block·next block →recent activity