← previous blocknext block →recent activity

Analyzing

Block #73,493,546

15 transactions · 12 stateful · 2026-05-09 16:28:25 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,493,546  ·  15 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

0x421d6551…436c

0x065c9d…c394

4 touches
2 conflicts

0x6af306bb…2e81

0x3bd359…433a

4 touches
1 conflict

0xce8bbe33…b72e

0x3bd359…433a

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0xf91b744e…9117

0x754704…b603

4 touches
1 conflict

0x261e3f15…f125

0xd32edf…ff58

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: 0x065c9d28…a9c394

2 conflicts on slot 0x421d6551d9…84436c

← previous block·next block →recent activity