← previous blocknext block →recent activity

Analyzing

Block #73,952,745

17 transactions · 13 stateful · 2026-05-11 19:40:46 UTC

Parallelism

88/100

Blocked

31%

Avg conflicts / tx

0.24

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,952,745  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x1c354dc0…96de

0x754704…b603

4 touches
1 conflict

0xf91b744e…9117

0x754704…b603

4 touches
1 conflict

0x2b9c6652…d14e

0x754704…b603

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

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: 0x754704bc…afb603

1 conflict on slot 0x1c354dc030…2b96de

← previous block·next block →recent activity