← previous blocknext block →recent activity

Analyzing

Block #73,653,552

18 transactions · 15 stateful · 2026-05-10 10:15:05 UTC

Parallelism

72/100

Blocked

40%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,653,552  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x5618dbe3…ca7b

0x34b655…2a6f

4 touches
1 conflict

0x7acde5e5…ac70

0x34b655…2a6f

4 touches
1 conflict

0xc34a0420…db6a

0x34b655…2a6f

4 touches
1 conflict

0x897cfde7…5aab

0x065c9d…c394

2 touches
0 conflicts

0xa349d489…7546

0x065c9d…c394

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

10 conflicts on slot 0xf2438038b6…475fa7

← previous block·next block →recent activity