← previous blocknext block →recent activity

Analyzing

Block #73,651,147

17 transactions · 13 stateful · 2026-05-10 09:58:53 UTC

Parallelism

59/100

Blocked

54%

Avg conflicts / tx

1.47

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,651,147  ·  17 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xb159af88…a9e7

0x065c9d…c394

14 touches
21 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x7f81fb82…633e

0x065c9d…c394

4 touches
1 conflict

0x9aacfd44…851d

0x065c9d…c394

3 touches
1 conflict

0x1af4b0d4…7389

0x065c9d…c394

3 touches
1 conflict

0xae69c125…2379

0x2a68ba…90c5

2 touches
0 conflicts

0xc9e97522…3519

0x2a68ba…90c5

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

21 conflicts on slot 0xb159af880b…47a9e7

← previous block·next block →recent activity