← previous blocknext block →recent activity

Analyzing

Block #73,488,226

12 transactions · 8 stateful · 2026-05-09 15:52:59 UTC

Parallelism

83/100

Blocked

25%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,488,226  ·  12 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

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x965d5b8a…b9f2

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x45457742…d614

0x065c9d…c394

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0xcc59417c…355c

0x065c9d…c394

3 touches
1 conflict

0x4aa3bafb…2ef4

0x065c9d…c394

3 touches
1 conflict

0xe20db839…7577

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

1 conflict on slot 0xf537eaa0c6…3873c8

← previous block·next block →recent activity