← previous blocknext block →recent activity

Analyzing

Block #73,384,154

11 transactions · 9 stateful · 2026-05-09 04:20:24 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,384,154  ·  11 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

0x8876d94c…8435

0x2a68ba…90c5

4 touches
1 conflict

0x80e5d303…ed94

0xa6afd3…d132

3 touches
1 conflict

0x6677f92f…b7cd

0x0555e3…2b9c

2 touches
0 conflicts

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x8edd456e…c7e3

0x0555e3…2b9c

2 touches
0 conflicts

0x69b2b8ff…ddc3

0x065c9d…c394

2 touches
0 conflicts

0x2877f440…c2c8

0x34b655…2a6f

2 touches
0 conflicts

0x47f811fd…2c07

0x34b655…2a6f

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x8876d94c2a…cc8435

← previous block·next block →recent activity