← previous blocknext block →recent activity

Analyzing

Block #73,748,886

38 transactions · 21 stateful · 2026-05-10 20:58:23 UTC

Parallelism

82/100

Blocked

57%

Avg conflicts / tx

0.87

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,748,886  ·  38 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

0xd5c78b01…1150

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x7f81fb82…633e

0x065c9d…c394

8 touches
6 conflicts

0xbc6ab02c…b780

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x15d039e7…4bb6

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf06c2cf5…61bd

0x34b655…2a6f

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

21 conflicts on slot 0xd5c78b01c7…e61150

← previous block·next block →recent activity