← previous blocknext block →recent activity

Analyzing

Block #73,921,120

16 transactions · 14 stateful · 2026-05-11 16:10:24 UTC

Parallelism

50/100

Blocked

57%

Avg conflicts / tx

1.56

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,921,120  ·  16 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

14 touches
21 conflicts

0xee230b20…5a0f

0x34b655…2a6f

8 touches
6 conflicts

0x1da1c6cb…bb3f

0x34b655…2a6f

6 touches
3 conflicts

0x2aef4269…ad47

0x34b655…2a6f

4 touches
1 conflict

0x2cf96c0a…538a

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x55b6a001…1e7a

0x34b655…2a6f

4 touches
1 conflict

0x7cbd466f…1700

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity