← previous blocknext block →recent activity

Analyzing

Block #73,695,997

18 transactions · 14 stateful · 2026-05-10 15:01:25 UTC

Parallelism

78/100

Blocked

29%

Avg conflicts / tx

0.28

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,695,997  ·  18 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

0xf2438038…5fa7

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x4d3e58e0…a2d7

0x34b655…2a6f

4 touches
1 conflict

0x9d74d480…1a9e

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

2 touches
0 conflicts

0xf1b9bc34…e1f1

0x065c9d…c394

2 touches
0 conflicts

0xae69c125…2379

0x2a68ba…90c5

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

3 conflicts on slot 0xf2438038b6…475fa7

← previous block·next block →recent activity