← previous blocknext block →recent activity

Analyzing

Block #73,693,644

11 transactions · 9 stateful · 2026-05-10 14:45:36 UTC

Parallelism

73/100

Blocked

33%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,693,644  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0xaa8a1c54…ead3

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x20990c4e…bd94

0x065c9d…c394

2 touches
0 conflicts

0x3001ee38…be7d

0x065c9d…c394

2 touches
0 conflicts

0x9ae804bb…ce2c

0x065c9d…c394

2 touches
0 conflicts

0xc3a97e75…1228

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: 0x065c9d28…a9c394

3 conflicts on slot 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity