← previous blocknext block →recent activity

Analyzing

Block #73,324,194

19 transactions · 14 stateful · 2026-05-08 21:41:37 UTC

Parallelism

79/100

Blocked

29%

Avg conflicts / tx

0.37

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,324,194  ·  19 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

0xb389d45f…8a4c

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x0a80ff36…d8d4

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x819ea6d6…cd6f

0x34b655…2a6f

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002d

0x1b6862…e19c

2 touches
0 conflicts

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 0xb389d45f2b…a98a4c

← previous block·next block →recent activity