← previous blocknext block →recent activity

Analyzing

Block #73,318,843

17 transactions · 9 stateful · 2026-05-08 21:06:00 UTC

Parallelism

88/100

Blocked

11%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,318,843  ·  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

0x0d0b2509…074d

0x3bd359…433a

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xe6455d1f…1029

0x754704…b603

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

2 touches
0 conflicts

0x76ec699c…3be5

0x065c9d…c394

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

2 touches
0 conflicts

0xa4e3b3b1…0911

0x2a68ba…90c5

2 touches
0 conflicts

0xa980598e…ec52

0x3bd359…433a

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: 0x3bd359c1…15433a

1 conflict on slot 0x0d0b2509ae…4b074d

← previous block·next block →recent activity