← previous blocknext block →recent activity

Analyzing

Block #73,670,592

7 transactions · 7 stateful · 2026-05-10 12:10:00 UTC

Parallelism

57/100

Blocked

43%

Avg conflicts / tx

0.57

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,670,592  ·  7 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

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xc21968d7…2d2d

0x065c9d…c394

4 touches
1 conflict

0x81752b62…0869

0x065c9d…c394

4 touches
1 conflict

0x12ee0db9…8df4

0x065c9d…c394

4 touches
1 conflict

0xba4fc30c…120e

0x065c9d…c394

3 touches
1 conflict

0x2bdac2c9…41db

0x065c9d…c394

3 touches
1 conflict

0x4ae2c599…0e51

0x065c9d…c394

3 touches
1 conflict

0xd13b2a8c…cfce

0x065c9d…c394

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

1 conflict on slot 0x046a928e85…e50012

← previous block·next block →recent activity