← previous blocknext block →recent activity

Analyzing

Block #73,917,678

9 transactions · 9 stateful · 2026-05-11 15:47:29 UTC

Parallelism

56/100

Blocked

44%

Avg conflicts / tx

0.78

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,917,678  ·  9 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

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x329248e1…561f

0x065c9d…c394

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0xaa87afc2…9ed1

0x065c9d…c394

3 touches
1 conflict

0x83e56ad9…1abd

0x065c9d…c394

3 touches
1 conflict

0x304aeb30…f07b

0x065c9d…c394

3 touches
1 conflict

0x477ec9fa…9907

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