← previous blocknext block →recent activity

Analyzing

Block #73,211,167

11 transactions · 11 stateful · 2026-05-08 09:09:38 UTC

Parallelism

64/100

Blocked

27%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,211,167  ·  11 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x7f189cf6…afab

0x065c9d…c394

6 touches
3 conflicts

0xcf284d5d…345b

0x065c9d…c394

4 touches
1 conflict

0x08cc9b00…c8a8

0x065c9d…c394

3 touches
1 conflict

0xd6521d2f…0ce7

0x065c9d…c394

3 touches
1 conflict

0x33e4f987…3d41

0x065c9d…c394

2 touches
0 conflicts

0x64ba364b…8f2b

0x065c9d…c394

2 touches
0 conflicts

0x965a6302…8cdf

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity