← previous blocknext block →recent activity

Analyzing

Block #73,343,409

16 transactions · 14 stateful · 2026-05-08 23:49:23 UTC

Parallelism

81/100

Blocked

14%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,343,409  ·  16 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

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0x2b9c6652…d14e

0x754704…b603

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

2 touches
0 conflicts

0x43f7c27e…0399

0x065c9d…c394

2 touches
0 conflicts

0x489cb750…7069

0x065c9d…c394

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0x00f7e3b7…e017

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

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

3 conflicts on slot 0xdd70bea3b0…701ffe

← previous block·next block →recent activity