← previous blocknext block →recent activity

Analyzing

Block #73,960,830

12 transactions · 11 stateful · 2026-05-11 20:34:28 UTC

Parallelism

42/100

Blocked

55%

Avg conflicts / tx

1.58

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,960,830  ·  12 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x35b85d8e…1edd

0x34b655…2a6f

6 touches
3 conflicts

0x874f5c70…608f

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xee230b20…5a0f

0x34b655…2a6f

6 touches
3 conflicts

0x7d1140c6…14a5

0x34b655…2a6f

4 touches
1 conflict

0x9b8800c1…ed12

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity