← previous blocknext block →recent activity

Analyzing

Block #73,698,400

8 transactions · 7 stateful · 2026-05-10 15:17:39 UTC

Parallelism

50/100

Blocked

43%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,698,400  ·  8 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

0x856d17ef…c545

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0xf94492b0…24d3

0x065c9d…c394

3 touches
1 conflict

0x02189e08…57a5

0x065c9d…c394

3 touches
1 conflict

0xae69c125…2379

0x2a68ba…90c5

2 touches
0 conflicts

0x0175b7a6…1db9

0x6c4bfa…a540

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

1 conflict on slot 0x856d17ef14…a5c545

← previous block·next block →recent activity