Block #73,683,141

← previous blocknext block →recent activity

Analyzing

Block #73,683,141

10 transactions · 9 stateful · 2026-05-10 13:34:52 UTC

Parallelism

70/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,683,141  ·  10 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

0xecd87a39…d9c5

0x34b655…2a6f

4 touches
1 conflict

0x71fc6c51…139a

0x065c9d…c394

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x411855c9…3eca

0x065c9d…c394

2 touches
0 conflicts

0x7110f7d8…27ab

0x065c9d…c394

2 touches
0 conflicts

0x88941951…1163

0x065c9d…c394

2 touches
0 conflicts

0xe884644d…b9ce

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: 0x34b6552d…112a6f

1 conflict on slot 0xecd87a399c…10d9c5

← previous block·next block →recent activity