← previous blocknext block →recent activity

Analyzing

Block #73,200,923

16 transactions · 16 stateful · 2026-05-08 08:01:31 UTC

Parallelism

56/100

Blocked

38%

Avg conflicts / tx

0.88

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,200,923  ·  16 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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x2a354a63…0515

0x065c9d…c394

8 touches
6 conflicts

0x4e5ebbf7…ae70

0xc8689a…ee79

6 touches
3 conflicts

0x8e66da19…66b6

0x065c9d…c394

6 touches
3 conflicts

0x0175b7a6…1dba

0x6ca43f…c331

6 touches
3 conflicts

0x0175b7a6…1dbb

0x6ca43f…c331

6 touches
3 conflicts

0x0175b7a6…1dbd

0x6ca43f…c331

6 touches
3 conflicts

0x1a4b4152…0a08

0x6ca43f…c331

6 touches
3 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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity