← previous blocknext block →recent activity

Analyzing

Block #73,270,923

19 transactions · 17 stateful · 2026-05-08 15:47:07 UTC

Parallelism

58/100

Blocked

41%

Avg conflicts / tx

1.47

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,270,923  ·  19 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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…0002

0xab3526…fa38

16 touches
28 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0fb0ffbc…fe8d

0x065c9d…c394

2 touches
0 conflicts

0x20f92b9c…ea55

0x065c9d…c394

2 touches
0 conflicts

0x22dbf14a…223d

0x065c9d…c394

2 touches
0 conflicts

0x2fc43a95…ad0e

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: 0xab35264b…1cfa38

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity