← previous blocknext block →recent activity

Analyzing

Block #73,655,101

29 transactions · 20 stateful · 2026-05-10 10:25:33 UTC

Parallelism

79/100

Blocked

50%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,655,101  ·  29 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xbf5e8a00…9a2a

0xd32edf…ff58

11 touches
15 conflicts

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x0175b7a6…1db9

0x6c4bfa…a540

4 touches
1 conflict

0x0175b7a6…1dba

0x6c4bfa…a540

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: 0xd32edf66…9fff58

15 conflicts on slot 0xbf5e8a00a5…e99a2a

← previous block·next block →recent activity