← previous blocknext block →recent activity

Analyzing

Block #73,683,178

32 transactions · 28 stateful · 2026-05-10 13:35:07 UTC

Parallelism

88/100

Blocked

43%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,683,178  ·  32 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x9ec6f9f2…5e23

0xd32edf…ff58

5 touches
3 conflicts

0x7c403af1…31b1

0x3bd359…433a

4 touches
1 conflict

0xd77e90ec…8c04

0x3bd359…433a

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x00000000…0004

0x5afd3e…7620

4 touches
1 conflict

0xa06bbbcb…d462

0x5afd3e…7620

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity