← previous blocknext block →recent activity

Analyzing

Block #73,955,719

19 transactions · 17 stateful · 2026-05-11 20:00:32 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,955,719  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xe93c34d9…3bc8

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

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

6 conflicts on slot 0xe93c34d939…123bc8

← previous block·next block →recent activity