← previous blocknext block →recent activity

Analyzing

Block #73,705,536

16 transactions · 14 stateful · 2026-05-10 16:05:48 UTC

Parallelism

75/100

Blocked

36%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,705,536  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xeebd31ac…0794

0x34b655…2a6f

6 touches
3 conflicts

0xe70f6c1d…2539

0x34b655…2a6f

6 touches
3 conflicts

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x15c9b5bf…f732

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: 0x34b6552d…112a6f

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity