← previous blocknext block →recent activity

Analyzing

Block #73,343,726

17 transactions · 15 stateful · 2026-05-08 23:51:29 UTC

Parallelism

71/100

Blocked

33%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,343,726  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xeeb66648…fa78

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0175b7a6…1dbc

0xaba216…a862

4 touches
1 conflict

0xa7f5e427…3b13

0xaba216…a862

4 touches
1 conflict

0xf0f673fd…37a7

0xaba216…a862

4 touches
1 conflict

0xd821ae10…fe17

0xc8689a…ee79

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0xbdff944d…447e

0x2a68ba…90c5

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: 0xd32edf66…9fff58

10 conflicts on slot 0xeeb66648e4…65fa78

← previous block·next block →recent activity